Meet us at WordCamp Kerala 2024 Conference to explore solutions. Know More
Contents
ASP.NET SAML Single Sign-On (SSO) with Okta As IDP
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.
Platform Support: The ASP.NET SAML SSO module supports ASP.NET 3.5
and above frameworks.
To set up the module, extract the file
asp.net-saml-sso-module-xxx.zip. You will find a DLL named
miniorange-saml-sso.dll, a configuration file named
saml.config and an integration.md file which contains
steps for adding the module into your application.
Add miniorange-saml-sso.dll into your bin folder (where other DLL
files for your application exist).
Register minorangesamlsso module in your application according to
the steps provided in the file named integration.md.
Add the provided configuration file saml.config in the root
directory of your application.
After integration, open your browser and browse the connector dashboard with
the URL below: https://<your-application-base-url>/?ssoaction=config
If the registration page or login page pops up, you have successfully added
the miniOrange SAML SSO connector to your application.
Register or log in with your account by clicking the Register button
to configure the module.
Steps to configure ASP.NET Single Sign-On (SSO) using Okta as IDP
1. Configure Okta as identity provider
You need to send your SP metadata to your identity provider. For SP
metadata, use the SP metadata URL or download the SP metadata as a .xml file
and upload it at your IdP end. You can find both these options under the
Service Provider Settings tab.
Alternatively, you can manually add the SP Entity ID and ACS URL from
Service Provider Settings tab in the plugin to your IdP
configurations.
In Okta Developer site, navigate to Applications tab and select
Applications.
Click on the Create App Integration button to create new app.
Click on the SAML 2.0.
In General Settings tab, enter App Name and click on
Next button.
In SAML Settings, enter the following:
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.
Configure Group Attribute Statements (Optional) and click on
Next button.
If you have integrated your Active Directory in Okta and want to map the AD
groups, please make sure that you have added the OUs used to import
groups.You will also need to map the member of attribute under the
integrated directory’s configuration.
Assigning Groups/People
After creating and configuring the app go to the
Assignment Tab in Okta.
Here we select the peoples and groups you want to give access to log in
through this app. Assign this to the people/group you would to give access
to.
After assigning the people/groups to your app, go to
Sign On tab.
Under SAML Signing Certificates, click on
View SAML setup instructions to get the
SAML Login URL (Single Sign on URL), Single Logout URL, IDP Entity ID and X.509 Certificate. You will need this to configure the
ASP.NET SAML Module.
2. Configure ASP.NET application as service provider (SSO Module)
Note: After installation of the plugin, we need to setup the trust
between your ASP.NET application and Okta. SAML metadata is shared with Okta
so they can update their inbuilt configuration to support Single Sign-On.
2.1: Share SAML Metadata with Okta
Click on Add New IDP to configure ASP.NET Single Sign-On (SSO) with
Okta.
Under Service Provider Settings tab, you can either copy-paste the
metadata URL on your IDP side or download the SP metadata as
an XML file. Additionally, you have the choice to manually copy and paste
Base URL, SP Entity ID, and ACS URL.
Share SAML metadata with your identity provider.
2.2: Import Okta SAML metadata
Select Okta from the list of identity providers shown below.
There are two ways detailed below with which you can configure your SAML
identity provider metadata in the module.
A] Upload metadata using the Upload IDP Metadata button:
If your identity provider has provided you with the metadata URL or metadata
file (.xml format only), then you can simply configure the identity provider
metadata in the module using the
Upload IDP Metadata option.
You may refer to the screenshot below:
You can choose any one of the options according to the metadata format you
have available.
B] Configure the identity provider metadata manually:
After configuring your identity provider, it will provide you with
IDP Entity ID, IDP Single Sign On URL
and SAML X509 Certificate fields respectively.
Click Save to save your IDP details.
You have successfully configured your ASP.NET application as a service
provider.
3. Testing SAML SSO
Before testing, please ensure the following:
The ASP.NET (SP) SAML metadata has been exported to Okta (IDP).
Importing the Okta (IDP) SAML metadata in ASP.NET (SP).
To test whether the SAML configuration you’ve done is correct, hover on
Select Actions and click on Test Configuration.
Note: In the trial version of the plugin, you can only configure and
test one identity provider (IDP).
The screenshot below shows a successful result. Click on
Done to further continue with the SSO Integration.
If you are experiencing any error on the module end you’ll be shown with the
window similar to below.
To troubleshoot the error you can follow the below steps:
Under
Troubleshooting
tab, enable the toggle to receive the plugin logs.
Once enabled, you will be able to retrieve plugin logs by navigating to
Identity Provider Settings tab and clicking on
Test Configuration.
Download the log file from the Troubleshoot tab to see what
went wrong.
You can share the log file with us at
aspnetsupport@xecurify.com
and our team will reach out to you to resolve your issue.
4. Integration Code
This step allows you to specify the sso prefix of the session or claims
parameter that will be used to access user attributes in your application.
If you're still confused about how the integration steps work, take a look
at the Setup Tour.
Select the mode for storing SSO attributes, and you will now see the
integration code based on the authentication method you selected and
the language your application uses.
Just copy-paste that code snippet wherever you want to access the user
attributes.
Note: This trial module only supports session-based authentication
and User Claims is available in the premium plugin.
Note: All the mapped attributes will be stored in the session so that
you can access them in your application.
If you want some assistance regarding the integration code, get in touch
with us at
aspnetsupport@xecurify.com
5. Login Settings
Hover on Select Actions and click on Copy SSO Link.
Use the copied link in the application from where you want to perform SSO:
https://base-url/?ssoaction=login
For example, you can use it as: <a href=”https://base-url/?ssoaction=login”>Log in</a>
6. Logout Settings
Use the following URL as a link in your application from where you want to
perform SLO:
https://<your-application-base-url>/?ssoaction=logout
For example you can use it as:
<a
href="https://<your-application-base-url>/?ssoaction=logout">Logout</a>
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
aspnetsupport@xecurify.com
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.
×
Trending searches:
Hello there!
Need Help? We are right here!
Contact miniOrange Support
Thanks for your inquiry.
If you dont hear from us within 24 hours, please feel free to send a follow up email to info@xecurify.com
Cookie Preferences
Cookie Consent
This privacy statement applies to miniorange websites describing how we handle the personal
information.
When you visit any website, it may store or retrieve the information on your browser, mostly in the
form of the cookies. This information might be about you, your preferences or your device and is
mostly used to make the site work as you expect it to. The information does not directly identify
you, but it can give you a more personalized web experience.
Click on the category headings to check how we handle the cookies.
For the privacy statement of our solutions you can refer to the privacy policy.
Strictly Necessary Cookies
Always Active
Necessary cookies help make a website fully usable by enabling the basic functions like site
navigation, logging in, filling forms, etc. The cookies used for the functionality do not store any
personal identifiable information. However, some parts of the website will not work properly without
the cookies.
Performance Cookies
Always Active
These cookies only collect aggregated information about the traffic of the website including -
visitors, sources, page clicks and views, etc. This allows us to know more about our most and least
popular pages along with users' interaction on the actionable elements and hence letting us improve
the performance of our website as well as our services.