Meet us at WordCamp Kerala 2024 Conference to explore solutions. Know More
Contents
Umbraco SAML Single Sign-On (SSO) with Okta as IDP
Umbraco SAML Single Sign-On (SSO)
plugin gives the ability to enable SAML Single Sign-On for your Umbraco
applications. Using Single Sign-On you can use only one password to access
your Umbraco application and services. Our plugin 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 Umbraco and Okta considering
Okta as IdP. To know more about the features we provide for Umbraco SSO, click
here.
Select your umbraco version to configure SSO with:
Download
Umbraco SAML Single Sign-On (SSO) module.
For Setting up the module, extract the
umbraco-saml-sso-connector.zip, you will find a DLL file
miniorange-saml-sso.dll, a configuration file
saml.config and a integration.md file which contain the
steps for adding the module into your application.
Add miniorange-saml-sso.dll in the bin folder (where your other
DLL files exist) for your Umbraco site.
Register miniorangesamlsso module for your umbraco SSO
according to the provided steps in the integration.md file.
Add the provided configuration file saml.config in the root
directory for your umbraco site.
Download
Umbraco SAML Single Sign-On (SSO) middleware.
For Setting up the middleware, you will be required to add the below namespaces, services and middleware
in your startup.cs file (marked in green), below here is a sample example
using miniorange.saml;using System.Reflection;namespace Application{public class Startup{ // Add services to the container. public void ConfigureServices(IServiceCollection services) { services.AddUmbraco(_env, _config) .AddBackOffice() .AddWebsite() .AddComposers() .Build(); services.AddminiOrangeServices(Assembly.GetExecutingAssembly()); } public void Configure(IApplicationBuilder app, IWebHostEnvironment env) { if (env.IsDevelopment()) { app.UseDeveloperExceptionPage(); } app.UseUmbraco() .WithMiddleware(u => { u.UseBackOffice(); u.UseWebsite(); u.AppBuilder.UseminiOrangeSAMLSSOMiddleware(); }) .WithEndpoints(u => { u.UseInstallerEndpoints(); u.UseBackOfficeEndpoints(); u.UseWebsiteEndpoints(); }); } } }
Run the application when the configuration is done.
After integration, open your browser and browse the plugin dashboard
with the URL below:
https://<umbraco-middleware-base-url>/?ssoaction=config
If the registration page or login page pops up, you have successfully
added the miniOrange Umbraco SAML middleware in your Umbraco
application.
Register or log in with your account by clicking the
Register button to configure the plugin
Download
Umbraco SAML Single Sign-On (SSO) middleware.
For Setting up the middleware, you will be required to add the below namespaces, services and middleware
in your program.cs file (marked in green), below here is a sample example
Run the application when the configuration is done.
After integration, open your browser and browse the plugin dashboard
with the URL below:
https://<umbraco-middleware-base-url>/?ssoaction=config
If the registration page or login page pops up, you have successfully
added the miniOrange Umbraco SAML middleware in your Umbraco
application.
Register or log in with your account by clicking the
Register button to configure the plugin
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 Umbraco SAML SSO connector to your application.
Register or log in with your account by clicking the
Register button to configure the module.
Configure Umbraco Single Sign-On (SSO) using Okta as IDP
1. Configure Okta as IDP
There are below two ways with which you can get the SAML SP metadata to
configure on your Okta end.
A] Using SAML metadata URL or metadata file:
Under the Service Provider Settings section, you can find the
metadata URL as well as the option to download the SAML metadata
Copy metadata URL or download metadata file to configure the same on your
Okta end.
You can refer to the below screenshot:
B] Uploading metadata manually:
From the Service Provider Settings section, you can copy the service
provider metadata manually like SP Entity ID, ACS URL, Single Logout URL,
and provide it to your identity provider for configuration.
You can refer to the below screenshot:
Under the Plugin Settings tab, select Okta as your identity
provider from the list shown below:
There are two ways detailed below with which you can get the SAML SP
metadata to configure onto your Okta end.
A] Using SAML metadata URL or metadata file:
In the Plugin Settings menu, look for Service Provider settings.
Under that, you can find the metadata URL as well as the option to
download the SAML metadata.
Copy metadata URL or download the metadata file to configure the same on
your Okta end. You may refer to the screenshot below:
B] Uploading metadata manually:
From the Service Provider settings section, you can manually copy
the service provider metadata like SP Entity ID, ACS URL,
Single Logout URL and share it with your identity provider for
configuration. You may refer to the screenshot below:
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 memberOf 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.
You have successfully configured Okta as SAML IdP (Identity Provider) for
achieving Umbraco Single Sign-On (SSO), ensuring secure Okta Login into
Umbraco application.
2. Configure Umbraco as Service Provider
There are below two ways 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 simply configure the identity
provider metadata in the module using the
Upload IdP Metadata option.
You can refer to the below screenshot
You can choose any one of the options according to the metadata format you
are available with.
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 x.509 Certificate.
Configure these values under IDP Entity ID, Single Sign-On URL and
SAML X509 Certificate fields respectively.
Click Save to save your IDP details.
You have successfully configured your Umbraco application as a service
provider.
There are two ways detailed below with which you can get the SAML SP metadata to configure onto your identity provider end.
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 plugin 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
There are two ways detailed below with which you can configure your SAML
identity provider metadata in the plugin.
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 plugin 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
3. Testing SAML SSO
Click on the Test Configuration button to test whether the SAML Configuration you’ve done is correct.
The screenshot below shows a successful result. Click on SSO Integration 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
umbracosupport@xecurify.com
and our team will reach out to you to resolve your issue.
Click on the Test Configuration button to test whether the SAML Configuration you’ve done is correct.
The screenshot below shows a successful result. Click on SSO Integration 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
umbracosupport@xecurify.com
and our team will reach out to you to resolve your issue.
Click on the Test Configuration button to test whether the SAML Configuration you’ve done is correct.
The screenshot below shows a successful result. Click on SSO Integration 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
umbracosupport@xecurify.com
and our team will reach out to you to resolve your issue.
4. Login Settings
Go to Select Actions and click on Copy SSO Link.
Use the copied link in the application from where you want to perform SSO
For example you can use it as: <a href="copied-sso-link”>Login</a>"
Use the following URL as a link in the application from where you want to
perform SSO:
https://<umbraco-middleware-base-url>/?ssoaction=login
Use the following URL as a link in the application from where you want to
perform SSO:
https://<umbraco-middleware-base-url>/?ssoaction=login
5. Logout Settings
Use the following URL as a link in your Umbraco from where you want to
perform SLO: https://umbraco-middleware-base-url/?ssoaction=logout
For example you can use it as: <a
href="https://umbraco-middleware-base-url/?ssoaction=logout”>Logout</a>"
You can even configure the
nopCommerce SAML Single Sign-On (SSO)
module with any identity providers 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. Check the list of identity
providers
here.
You can even configure the
nopCommerce SAML Single Sign-On (SSO)
module with any identity providers 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. Check the list of identity
providers
here.
Not able to find your identity provider? Mail us on
umbracosupport@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.