-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
relay_state should not be included in signing calculation when it is null #13913
Comments
Hi, @fr2lancer, thanks for the report. Is the empty relay state property causing you problems with the signature? |
Hi. Thanks for the reply. Yes it has caused auth request signing mismatch error with Azure. |
Is there any reason why you do not want to add the relay state parameter? I'm just trying to understand your use case. |
Hi. |
Hi, @fr2lancer. I don't think I follow exactly what you meant in your last comment, can you elaborate more on that? |
Hi the example is AuthRequest=AAA -> (no RelayState) this is data what my app send to IDP so this string is to be calculated in sign however in the current logic, AuthRequest=AAA&RelayState= is used to calculated in the signing. even RelayState value is not providided. So it causes mismatch. |
Describe the bug
Relay Status is optional value so if it is not provided or empty value, it doesn't need to be in signing calculation
To Reproduce
Expected behavior
should be included optionally when it is not empty or null.
The text was updated successfully, but these errors were encountered: