We are currently trying to implement external logins with OpenIdConnect, following the guide in the Documentation.
The redirect_uri field in our request is being built as http instead of https, which causes Azure AD to throw an error (our tenant specifically requires https urls).
Our server is located behind an AWS application load balancer which is terminating HTTPS ahead of the server.
We have been following This Guide as the basis for the OpenIdConnect implementation.
Errors with Backoffice External Login implementation with OpenIdConnect
Hello,
We are currently trying to implement external logins with OpenIdConnect, following the guide in the Documentation.
The redirect_uri field in our request is being built as http instead of https, which causes Azure AD to throw an error (our tenant specifically requires https urls).
Our server is located behind an AWS application load balancer which is terminating HTTPS ahead of the server.
We have been following This Guide as the basis for the OpenIdConnect implementation.
We have additionally tried the techniques in this Microsoft documentation article, but it doesn't seem to have any effect on the error.
Manually editing the redirect_uri field like this stack overflow post causes a 404 when redirecting to the redirect_uri.
Any input is appreciated!
- Colton Crouch
We have solved the issue. Following this guide to add the app.Use() section allowed the URI to be served as HTTPS. Hope this helps someone else!
is working on a reply...