4:54 p.m.
I currently work on KEYCLOAK-6073 (Support different URLs for front and
back channel requests in adapters) and try to implement some kind of
integration test, to verify that an adapter actual use its configured
url for backchannel requests.
When I understand the existing integration tests correct, it should be
relative easy to trigger most of the actions that execute backchannel
requests
(code-to-token, logout, etc.) with an adapter test
(AbstractExampleAdapterTest, AbstractServletsAdapterTest). But I don't
see a straight forward way how to verify the url that was actual used by
the adapter (in the deployed example or servlet).
Not sure if I am on the right track, so any thoughts on how to approach
this are appreciated. :)
Thanks
Luca
5:38 p.m.
One option could be to use an invalid URL for the front-end URL.
On Wed, 5 Jun 2019, 17:23 Luca Graf, <lucagraf(a)gmx.de> wrote:
I currently work on KEYCLOAK-6073 (Support different URLs for front
and
back channel requests in adapters) and try to implement some kind of
integration test, to verify that an adapter actual use its configured
url for backchannel requests.
When I understand the existing integration tests correct, it should be
relative easy to trigger most of the actions that execute backchannel
requests
(code-to-token, logout, etc.) with an adapter test
(AbstractExampleAdapterTest, AbstractServletsAdapterTest). But I don't
see a straight forward way how to verify the url that was actual used by
the adapter (in the deployed example or servlet).
Not sure if I am on the right track, so any thoughts on how to approach
this are appreciated. :)
Thanks
Luca
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev
6:38 p.m.
I like the idea and it should be possible to cover all cases without
needing any frontchannel communication at all. In the end it should make
no difference if the token endpoint was called during a direct flow or a
standard flow.
Thanks for the input, i will give it try in the next days.
Luca
On 05.06.19 17:38, Stian Thorgersen wrote:
One option could be to use an invalid URL for the front-end URL.
On Wed, 5 Jun 2019, 17:23 Luca Graf, <lucagraf(a)gmx.de
<mailto:lucagraf@gmx.de>> wrote:
I currently work on KEYCLOAK-6073 (Support different URLs for
front and
back channel requests in adapters) and try to implement some kind of
integration test, to verify that an adapter actual use its configured
url for backchannel requests.
When I understand the existing integration tests correct, it should be
relative easy to trigger most of the actions that execute backchannel
requests
(code-to-token, logout, etc.) with an adapter test
(AbstractExampleAdapterTest, AbstractServletsAdapterTest). But I don't
see a straight forward way how to verify the url that was actual
used by
the adapter (in the deployed example or servlet).
Not sure if I am on the right track, so any thoughts on how to
approach
this are appreciated. :)
Thanks
Luca
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org <mailto:keycloak-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/keycloak-dev
1780
days inactive
1780
days old
2 comments
2 participants
participants (2)
-
Luca Graf -
Stian Thorgersen