future-table-2431
12/11/2023, 7:57 PMKratos
(v1.0.0) , Hydra
(v2.1.0) and the kratos-selfservice-ui-node (v0.13.0-4 but also v.1.0.0 seems to play ok), to play all together.
After some trial and error, pretty much everything I need plays ok, apart from when I need to trigger logout from my app and call: {HYDRA_PUBLIC_URL}/oauth2/sessions/logout
(including id_token_hint
and only that till now).
It will redirect to /logout?logout_challenge=.... , which seems to not be supported till the v1.0.0 tag in the kratos-selfservice-ui-node
so I am getting a 404.
If I use the latest changes in master
for kratos-selfservice-ui-node
, then the route is triggered (it exists) but I am getting a
[....] kratos-selfservice-ui-node/src/pkg/middleware.ts:109:19 Error: Expected CSRF token middleware to be set but received none. [...]
Same happens if I do some tests using this example here: https://github.com/ory/examples/tree/master/kratos-hydra so my questions are:
• Was this above example supposed to work or at that point it was just a reference and the logout flow was not expected to function anyway?
• Is there an other working "out of the box" case for the logout (haven't tried the hydra-login-consent-node
), or someone should just go ahead and do their custom endpoint to interact with the backends? Just asking as I had initially hoped I could stitch up a package with existing solutions, in order to quickly test a PoC
thanks for any responses, in the meantime I 'll try to anonymize some of my config to make it available to some fresher eyes.future-table-2431
12/11/2023, 8:21 PMkratos-selfservice-ui-node
, good news is, I tried hydra-login-consent-node
(v2.1.0) and the implementation there works just fine.