-
Notifications
You must be signed in to change notification settings - Fork 429
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
urlHandler callback function parameter in LogoffRevocationService.logoff does nothing #966
Comments
Hey @Lexa-tech , So your issue is that you want to add custom params to the logoff url, is that correct? Thanks :) |
Exactly, I would like add state parameter when calling logoff function , the same way we can pass this state when calling the authorize function (with oidcService.setState ). |
So something like |
just need to check if the endsession endpoint allows custom parameters per spec. cheers Damien |
Couldn't you use the state that is set with the oidcService.setState method when calling logoff function ? |
Hi @damienbod , did you find your answer about allowing custom parameters in the endsession endpoint ? |
We will implement that. Just did not find the time until now. This is a breaking change. |
Related #932 |
Implemented, will be in Release 12. |
Thanks @FabianGosebrink |
Hello, I'm trying to add state parameter when calling logoff function.
The setState method in oidcService enable to pass this state parameter when calling authorize function, but this state is not added to the request when calling logoff functions.
That's why I'm trying to use urlHandler callback function parameter in logoff function, but it seems that it does nothing.
angular-auth-oidc-client/projects/angular-auth-oidc-client/src/lib/logoffRevoke/logoff-revocation.service.ts
Line 27 in 23ed172
Describe the bug
Impossible to add customParameter in logoff function.
Expected behavior
Pass state parameter when calling logoff functions
Desktop (please complete the following information):
Thanks for your Help
The text was updated successfully, but these errors were encountered: