ASP.NET SAML Single Sign-On (SSO) module gives the ability to enable SAML Single Sign-On for your ASP.NET applications. Using Single Sign-On you can use only one password to access your ASP.NET application and services. Our module is compatible with all the SAML compliant identity providers. Here we will go through a step-by-step guide to configure Single Sign-On (SSO) between ASP.NET and Okta considering Okta as IdP. To know more the other features we provide, click here.
Configure Okta as IdP
|Single Sign On URL||Enter ACS (AssertionConsumerService) URL from the Service Provider metadata tab of the module.|
|Audience URI (SP Entity ID)||Enter SP Entity ID / Issuer from the Service Provider Metadata tab of the module.|
Note: After installation of the plugin, we need to setup the trust between your ASP.NET application and your Okta account. SAML metadata is shared with Okta so they can update their inbuilt configuration to support Single Sign-On.
You can even configure the DNN SAML Single Sign-On (SSO) module with any identity provider such as ADFS, Azure AD, Bitium, centrify, G Suite, JBoss Keycloak, Okta, OneLogin, Salesforce, AWS Cognito, OpenAM, Oracle, PingFederate, PingOne, RSA SecureID, Shibboleth-2, Shibboleth-3, SimpleSAML, WSO2 or even with your own custom identity provider. To check other identity providers, click here.
Not able to find your identity provider? Mail us on firstname.lastname@example.org and we'll help you set up SSO with your IDP and for quick guidance (via email/meeting) on your requirement and our team will help you to select the best suitable solution/plan as per your requirement.
Need Help? We are right here!