-
Notifications
You must be signed in to change notification settings - Fork 122
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
Recognise absolute oauth2 callback-uri as absolute and don't append it to the base uri #370
Comments
@brent777 What is the use case for providing the full URL there? The host resolver should resolve the current server URL |
It seems like this feature does not work anymore. Micronaut v. 2.1.4 |
@nikomakela As you can see in the commit we have a test for this case. If there is a problem please file a new issue with an example app to reproduce |
Hi! Did this change was merged? I see the change in the commit Line 114 in e94a521
But it doesn't appear in the tag So neither in the latest So, are you going to merge this or should I implement Thanks :) |
Would it be possible for the callback-uri to be recognised as absolute if it begins with http / https? Right now, it is considered relative no matter what, it seems.
I need to do this to try workaround a very strange issue that I experience with my Micronaut app in some environments (but not all) where it is trying to make the callback over http instead of https (no idea why since my application endpoints are available over https only). My hope is if this URI could be configured as absolute, then I could explicitly put "https" in the URI and work around this strange issue.
Steps to Reproduce
callback-uri: https://xxxx/oauth/callback/azure
Run the application and try authenticate.
Notice that the callback URI sent to the auth provider appends this value to the base URI, i.e. https://xxxx/https://xxxx/oauth/callback/azure causing auth to fail.
Expected Behaviour
If I configure the callback-uri as https://xxxx/oauth/callback/azure, then I would expect it to be sent to the provider as https://xxxx/oauth/callback/azure and not https://xxxx/https://xxxx/oauth/callback/azure.
Actual Behaviour
It is sent to the provider as https://xxxx/https://xxxx/oauth/callback/azure.
Environment Information
Example Application
The text was updated successfully, but these errors were encountered: