-
Notifications
You must be signed in to change notification settings - Fork 210
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
[Feature Request] ForceHttpsRedirectUris option to elegantly enable container deployments #175
Comments
jmprieur
changed the title
[Feature Request]
[Feature Request] ForceHttpsRedirectUris option to elegantly enable container deployments
May 26, 2020
7 tasks
This was referenced Jun 11, 2020
Thanks, works great! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Initially raised by @krispenner in #115 (comment)
Is your feature request related to a problem? Please describe.
For many people who only want to ensure https is used (instead of http) like myself as I'm running in a Docker container hosted in Azure App Service. I think a simpler option such as ForceHttpsRedirectUris = true in the configuration/options would be simpler. It would remove the need to specify the full absolute URI just to ensure https is used allowing the computed redirect URI to stay and just upgrade it to https. I'm concerned with managing the absolute URIs across configuration files and environments - relative paths as so much friendlier.
Describe the solution you'd like
Here is what I've currently done which solved my issue of http being used when in a Docker container:
services.Configure(OpenIdConnectDefaults.AuthenticationScheme,
options => {
var redirectToIdpHandler = options.Events.OnRedirectToIdentityProvider;
options.Events.OnRedirectToIdentityProvider = async context =>
{
// Call what Microsoft.Identity.Web is doing
await redirectToIdpHandler(context);
Describe alternatives you've considered
Customers are not blocked as they can set the
RedirectUri
andPostLogoutRedirectUri
Additional context
This is a nice to have that would avoid devs maitaining multiple appsettings.json, in particular when there are several deployment slots ...
The text was updated successfully, but these errors were encountered: