ASP.NET SAML SP 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.
https://<your-application-base-url>?ssoaction=config
Follow the steps below to configure Okta as IdP
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. |
Assigning Groups/People
https://<your-application-base-url>/?ssoaction=login
<a href="https://<your-application-base-url>/?ssoaction=login">Login</a>
https://<your-application-base-url>/?ssoaction=logout
<a href="https://<your-application-base-url>/?ssoaction=logout">Logout</a>
You can configure the ASP.NET SAML 2.0 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.
If you are looking to Single Sign-On into your sites with any SAML compliant Identity Provider then we have a separate solution for that. We do provide SSO solutions for the following:
Application | LINK |
SAML SSO into DotNetNuke (DNN) site | Click here |
SAML SSO into SiteFinity site | Click here |
SAML SSO into Umbraco site | Click here |