IGA 4.2 blank landing page - The issuer returned by the OAuth Issuer does not match the OAuth Issuer URL

Hi!

We do have a freshly installed IGA 4.2 that starts without any errors in catalina log
Using IGA ond OSP installed on the same Windows server ...

When trying to access the site using fqdn (https://iga.domain.td) I get redirected to a blank page https://iga.domain.td/#/landing .

When checking in DevTools in Edge there is a error:

"Uncaught - The issuer returned by the OAuth Issuer (servername.domain.td/.../oauth2) does not match the OAuth Issuer URL (iga.domain.td/.../oauth2)

Any Ideas ?

/Peter

Parents
  • Is OSP running on the same box as IGA? (Does not have to).

    Dos the certificate used for SSL on  the IGA server have the Subject Alternate name that nmtches the URL you start on (iga.domain.td)?

    See how OAUth issuer is servername, but the the URL is iga?  before the domain.td parts?  Should be consistent and the same.

  • OSP is running on the same box as IGA and we do use a certificate with common name "iga.domain.td" and with SAN "server.domain.td".

    I tried changeing all config (URLs, Hosts) in IGA to be the same as "server.domain.iga" and then it works, but thats not how i want it to bee ... I'll about to try changeing the certificate to only common name

    It seems that the "Oauth Issuer" name does not come from any config. How is it created/choosen by the application?

Reply
  • OSP is running on the same box as IGA and we do use a certificate with common name "iga.domain.td" and with SAN "server.domain.td".

    I tried changeing all config (URLs, Hosts) in IGA to be the same as "server.domain.iga" and then it works, but thats not how i want it to bee ... I'll about to try changeing the certificate to only common name

    It seems that the "Oauth Issuer" name does not come from any config. How is it created/choosen by the application?

Children