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
I think this happens because in this line ResolveReference is used which has the following behaviour for merging paths:
return a string consisting of the reference's path component
appended to all but the last segment of the base URI's path (i.e.,
excluding any characters after the right-most "/" in the base URI
path, or excluding the entire base URI path if it does not contain
any "/" characters).
Expected behavior
The correct URL would be https://something.onelogin.com/oidc/2/.well-known/openid-configuration
Additional context to reproduce
No response
Screenshots
No response
Are you sure this issue hasn't been raised already?
Yes
Have you read the Code of Conduct?
Yes
The text was updated successfully, but these errors were encountered:
The issue you're describing seems to be related to how the ResolveReference method constructs the redirect path in the Flyte admin server's authentication handler. This method appends the reference's path component to all but the last segment of the base URI's path, which can lead to incorrect URL construction.
To address this, you might need to modify the way the URL is constructed in the Flyte admin server's code. Specifically, you should ensure that the base URL is correctly appended with the desired path.
Would you like more detailed guidance on how to modify the code to fix this issue?
Describe the bug
Let's assume the following configuration:
Then request to Flyte's
/.well-known/openid-configuration
returns HTTP Code 303 (See Other) with the following header:I think this happens because in this line ResolveReference is used which has the following behaviour for merging paths:
Expected behavior
The correct URL would be
https://something.onelogin.com/oidc/2/.well-known/openid-configuration
Additional context to reproduce
No response
Screenshots
No response
Are you sure this issue hasn't been raised already?
Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: