Timeline for Error while configuring Access Management with OpenID Connect identity provider
Current License: CC BY-SA 4.0
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 25, 2022 at 12:19 | comment | added | Prasanna K Gollamudi | @Velu Thank you very much for your help | |
| Jan 25, 2022 at 12:12 | comment | added | Velmurugan♦ | @PrasannaKGollamudi: It depends. if your access management planned to run in HTTPS. then you have to keep the HTTPS redirect URL in azure, if it's HTTP then yes you can keep the HTTP redirect URL | |
| Jan 25, 2022 at 11:25 | comment | added | Prasanna K Gollamudi | Small clarification: Can we configure Non SSL Url as Redirect Url in Azure | |
| Jan 25, 2022 at 11:20 | vote | accept | Prasanna K Gollamudi | ||
| Jan 25, 2022 at 10:24 | comment | added | Velmurugan♦ | @PrasannaKGollamudi, If the answer helped to fix your issue, please upvote and accept the answer, to answer your question. if you want to keep it in the same CMS server then still possible, but keep it like that, CME is in 443 it should be accessible cms-domain.com for access management keep it cms-domain.com:85/access-management, don't use a proxy redirect. if you looking to keep running both 443 port it's not advised. | |
| Jan 25, 2022 at 9:36 | comment | added | Prasanna K Gollamudi | @velu , Client requested that we need to configure same domain as CMS for Access management also, so we tried to install Access management on CMS server with port :84 and tried to utilize IIS rewrite module to redirect to "localhost:84" if our CMS url which hosted on 443 contains "access-management" by SSL offloading, that didnt worked, can you please suggest if there is any other way I can achieve the requirement | |
| Jan 10, 2022 at 16:25 | comment | added | Velmurugan♦ | @PrasannaKGollamud localhost setup is only if you install everything on one server. For customer environments, better to install access and add-services in separate shared servers. expose it with a DNS name to make sure it's accessible to CME and DXD services. yes you can use https://<your-accessmangement-host>:8443 | |
| Jan 10, 2022 at 11:42 | comment | added | Prasanna K Gollamudi | few clarifications: 1. As per documentation we should not install Access Management in Same as CMS server if we configure "local host" in another server CMS may not be able to access the configured URL, will it not create any issue? 2. If we configure localhost will Azure Ad recognizes that URL and provide access token? 3. Can I use port 8443 instead 443 to configure windows service in CMS server. | |
| Jan 7, 2022 at 16:02 | comment | added | Velmurugan♦ | It depends which URL you are going to use and configure in CME it has to be, localhost URL can also work. localhost/access-management/azuread/signin-oidc, make sure to add signin-oidc for the redirect, not signout, makes sure whatever the access management URL you are going to configure in CME same domain should be configured in azure redirect url. | |
| Jan 7, 2022 at 15:27 | comment | added | Prasanna K Gollamudi | Once installed redirect url of access management showed as "localhost:84/access-management/azuread/signout-oidc" after enabling HTTPS should we configure in azure as "localhost:443/access-management/azuread/signout-oidc" or do we need to configure domain name or localhost works? | |
| Jan 6, 2022 at 12:47 | comment | added | Velmurugan♦ | @PrasannaKGollamudi yes. if you created a certificate with DNS name tridiondemo.com then that certificate subject become tridiondemo.com, In case if you are using a wildcard certificate then need to use *.tridiondemo.com | |
| Jan 6, 2022 at 11:41 | comment | added | Prasanna K Gollamudi | Can the Subject be same Domain as CMS? I am installing Access Management on CMS server. for example if my CMS Url is tridiondemo.com can the Subject also be tridiondemo.com | |
| Jan 6, 2022 at 9:59 | history | edited | Velmurugan♦ | CC BY-SA 4.0 |
added 1454 characters in body
|
| Jan 6, 2022 at 9:59 | comment | added | Velmurugan♦ | No, Updated my answer, I will extend this script to support HTTPS later | |
| Jan 6, 2022 at 7:31 | comment | added | Prasanna K Gollamudi | Hi Velu, I have used the PowerShell script for Access Management installation, since I am not aware of sequence after Access Management installation we connected with our Azure team. Your script works great. Small doubt Can I enable HTTPS Access Management directly using your PowerShell script by changing the $setupOptions.PORT_ACESSMANAEMENT_SERVICE value as 443. | |
| Jan 5, 2022 at 17:25 | history | answered | Velmurugan♦ | CC BY-SA 4.0 |