IMPORTANT!
This forum is now archived. Click here for the New Support Forum
Failed to determine the https port for redirect
Quote from elrenatom on March 20, 2019, 12:37 pmHello,
The error occurs only in production enviromnent, I have this error bellow:
2019-03-19T11:01:46.3450759-07:00 0HLLCIJPQ5UGQ:00000001 [WRN] Failed to determine the https port for redirect. (ca76cc21)
2019-03-19T11:02:03.5831975-07:00 0HLLCIJPQ5UGU:00000002 [WRN] CorsPolicyService did not allow origin: "https://vippersonaldance.com.br" (f5320bfb)
When I access the : https://vippersonaldance.com.br/.well-known/openid-configuration
The result is:
{"issuer":"http://vippersonaldance.com.br","jwks_uri":"http://vippersonaldance.com.br/.well-known/openid-configuration/jwks","authorization_endpoint":"http://vippersonaldance.com.br/connect/authorize","token_endpoint":"http://vippersonaldance.com.br/connect/token","userinfo_endpoint":"http://vippersonaldance.com.br/connect/userinfo","end_session_endpoint":"http://vippersonaldance.com.br/connect/endsession","check_session_iframe":"http://vippersonaldance.com.br/connect/checksession","revocation_endpoint":"http://vippersonaldance.com.br/connect/revocation","introspection_endpoint":"http://vippersonaldance.com.br/connect/introspect","device_authorization_endpoint":"http://vippersonaldance.com.br/connect/deviceauthorization","frontchannel_logout_supported":true,"frontchannel_logout_session_supported":true,"backchannel_logout_supported":true,"backchannel_logout_session_supported":true,"scopes_supported":["openid","profile","phone","email","roles","quickapp_api","offline_access"],"claims_supported":["sub","updated_at","locale","zoneinfo","birthdate","gender","website","picture","profile","preferred_username","nickname","middle_name","given_name","family_name","name","phone_number_verified","phone_number","email","email_verified","role","permission"],"grant_types_supported":["authorization_code","client_credentials","refresh_token","implicit","password","urn:ietf:params:oauth:grant-type:device_code"],"response_types_supported":["code","token","id_token","id_token token","code id_token","code token","code id_token token"],"response_modes_supported":["form_post","query","fragment"],"token_endpoint_auth_methods_supported":["client_secret_basic","client_secret_post"],"subject_types_supported":["public"],"id_token_signing_alg_values_supported":["RS256"],"code_challenge_methods_supported":["plain","S256"]} I don't know if the problem is this, but i think the correct is open id use "https:" instead of "https:", because inhttps://quickapp-pro.azurewebsites.net
works with https. how to solve this problem? (if I use the configuration options.RequireHttpsMetadata = true; // Note: Set to true in production ) I have problems with this enviroment when I click in Profile for example.
Hello,
The error occurs only in production enviromnent, I have this error bellow:
2019-03-19T11:01:46.3450759-07:00 0HLLCIJPQ5UGQ:00000001 [WRN] Failed to determine the https port for redirect. (ca76cc21)
2019-03-19T11:02:03.5831975-07:00 0HLLCIJPQ5UGU:00000002 [WRN] CorsPolicyService did not allow origin: "https://vippersonaldance.com.br" (f5320bfb)
When I access the : https://vippersonaldance.com.br/.well-known/openid-configuration
The result is:
{"issuer":"http://vippersonaldance.com.br","jwks_uri":"http://vippersonaldance.com.br/.well-known/openid-configuration/jwks","authorization_endpoint":"http://vippersonaldance.com.br/connect/authorize","token_endpoint":"http://vippersonaldance.com.br/connect/token","userinfo_endpoint":"http://vippersonaldance.com.br/connect/userinfo","end_session_endpoint":"http://vippersonaldance.com.br/connect/endsession","check_session_iframe":"http://vippersonaldance.com.br/connect/checksession","revocation_endpoint":"http://vippersonaldance.com.br/connect/revocation","introspection_endpoint":"http://vippersonaldance.com.br/connect/introspect","device_authorization_endpoint":"http://vippersonaldance.com.br/connect/deviceauthorization","frontchannel_logout_supported":true,"frontchannel_logout_session_supported":true,"backchannel_logout_supported":true,"backchannel_logout_session_supported":true,"scopes_supported":["openid","profile","phone","email","roles","quickapp_api","offline_access"],"claims_supported":["sub","updated_at","locale","zoneinfo","birthdate","gender","website","picture","profile","preferred_username","nickname","middle_name","given_name","family_name","name","phone_number_verified","phone_number","email","email_verified","role","permission"],"grant_types_supported":["authorization_code","client_credentials","refresh_token","implicit","password","urn:ietf:params:oauth:grant-type:device_code"],"response_types_supported":["code","token","id_token","id_token token","code id_token","code token","code id_token token"],"response_modes_supported":["form_post","query","fragment"],"token_endpoint_auth_methods_supported":["client_secret_basic","client_secret_post"],"subject_types_supported":["public"],"id_token_signing_alg_values_supported":["RS256"],"code_challenge_methods_supported":["plain","S256"]} I don't know if the problem is this, but i think the correct is open id use "https:" instead of "https:", because in
https://quickapp-pro.azurewebsites.net
works with https. how to solve this problem? (if I use the configuration options.RequireHttpsMetadata = true; // Note: Set to true in production ) I have problems with this enviroment when I click in Profile for example.
IMPORTANT!
This forum is now archived. Click here for the New Support Forum