• State Suggested Answer
  • Replies 11 replies
  • Answers 1 answer
  • Subscribers 95 subscribers
  • Views 5091 views
  • Users 0 members are here
Options
Related

No identity provider configure from Portal Web with Authetication Azure AD

jroberto moreno
over 3 years ago

I need deploy the portal web in a Site Web with the port 8443 and it authentication by Azure AD. I can not use "Default Web Site" because we need have different certificate.

Now, if I deploy the portal web in a SiteWeb with the port 8443, I get the error:

No identity provider configured

If I use the authentication de Active Directory, it work fine.

However, if I deploy the portal web in the "Default Web Site", it work fine and I can authentication by Azure AD.


Any idea?

Thanks!
Parents
  • 0 over 3 years ago

    Hello,

    the error thar I get is:

    2022-02-24 09:31:44.3839 ERROR (    WebLog gvj30c32xodjuggauhvwxwbt) : System.AggregateException: One or more errors occurred. ---> VI.Base.ViException: No identity provider configured.
       at QER.OAuthAuthentifier.OAuth.<_GetConfigAsync>d__38.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at QER.OAuthAuthentifier.OAuth.<GetConfigurationAsync>d__25.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at VI.DB.Auth.DbAuthenticator.<GetConfigurationAsync>d__9.MoveNext()
       --- End of inner exception stack trace ---

    Some idea?

  • 0 over 3 years ago in reply to jroberto moreno

    This error "No identity provider configured" is always due to the fact that the web application (IdentityManager) isn't configured properly to use OAuth.  Here's what I would check.

    1. In Designer, the URL "https://<yourwebsite>:8443/IdentityManager" must exists in the Base Data-> General->Web server configurations

    The above URL must MATCH the "BaseUrl" in your web.config file for the C:\inetpub\wwwroot\IdentityManager directory, or the location for your web site's application.

    2. Also in the "Web server configuration", the "OAuth 2.0/OpenID Connect application" must match the OAuth application you configured in the "OAuth 2.0/OpenID Connect configuration" in the Designer.

    The reason that it works if you switch to a URL without your port is that is is in the Web server configuration.  So for you to do what you want, you need two entries.  One for the default port and another for your custom port.

  • 0 over 3 years ago in reply to VilounV

    Hello,

    I have reviewed the two points and they are correct.

    Now, I don't undestand you comentary abour two entries. Two entries?

  • 0 over 3 years ago in reply to jroberto moreno

    If you want Identity Manager web portal to work with 443 and 8443, then you need two entries in the Web Server Configurations.

    If you only want 8443, then make sure all the things I mentioned are correct, IIS web.config, Designer web server configurations, and oauth web application.

Reply Children