You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please give us a thumbs up or thumbs down as a reaction to help us prioritize this feature. Feel free to comment if you have a particular need or comment on how this feature should work.
The text was updated successfully, but these errors were encountered:
Today I stumbled upon this. As far as I understand this would allow to add configuration option when initializing the SDK which in turn would set the configured logout redirect URL in post_logout_redirect_uri (right now logout will redirect to redirect_uri) ?.
Because right now we have to handle both login and logout actions using single route/endpoint, correct ?
Today I stumbled upon this. As far as I understand this would allow to add configuration option when initializing the SDK which in turn would set the configured logout redirect URL in post_logout_redirect_uri (right now logout will redirect to redirect_uri) ?. Because right now we have to handle both login and logout actions using single route/endpoint, correct ?
That is correct. This is an OIDC standard that fusionauth is compatible with. The SDKs just don't have an API that exposes it yet.
Add post_logout_redirect_uri to SDK configs
Problem
It appears that the hosted FA logout endpoint supports a
post_logout_redirect_uri
parameter, although the SDKs don't expose it to their configs.Solution
This could be a useful feature. It would be quite easy to implement, especially after #45 extracts the url tools to the core package.
Alternatives/workarounds
Don't add this feature.
Community guidelines
All issues filed in this repository must abide by the FusionAuth community guidelines.
How to vote
Please give us a thumbs up or thumbs down as a reaction to help us prioritize this feature. Feel free to comment if you have a particular need or comment on how this feature should work.
The text was updated successfully, but these errors were encountered: