miniOrange provides Single Sign-on for SAML apps. Security Assertion Markup Language (SAML) is an XML standard that allows secure web domains to exchange user authentication and authorization data. Using SAML, an online service provider (SP) can contact a separate online identity provider to authenticate users who are trying to access secure content.
miniOrange provides a solution to perform single sign-on(SSO) for application supporting SAML protocol like AWS, WordPress, Atlassian, Dropbox Enterprise, moodle, SAP, Zoho, zendesk, etc.
Configure Single Sign-On (SSO) Settings for SAML Apps:
1. Login as a customer from the Admin Console.
2. Go to Apps >> Manage Apps. Click on Configure Apps button.
3. Click on SAML tab. Select the Custom App.
4. If you can’t find your application in the below list, you can submit your app request to add the application as a pre-integrated app.
5. Once you select the Custom App option, you will find a window similar to :
- Either you can Copy Paste all the attributes of Service Provider (SP), Or you can directly upload an XML file containing relative information.
- To upload the file, follow these steps:
Click on Import SP Metadata button.
You will get a popup with following options.
URL : You get the URL for Metadata information from the Service Provider, you can directly add this URL in the input field provided
Text: When you select Text option, you will have to fill all the attributes manually
File: When you select File option, you can directly upload the XML file containing all the information.
- Here is the description what each field means (present on the app configuration window).
- SP Entity ID is used to identify your app against the SAML request received from SP. Make sure the SP Entity ID or Issuer is in this format: https://www.domain-name.com/a/[domain_name]/acs.
- ACS URL or Assertion Consumer Service URL defines where the SAML Assertion should be sent after authentication. Make sure the ACS URL is in the format: https://www.domain-name.com/a/[domain_name]/acs.
- Single Logout URL defines where the user should be redirected after receiving the logout request from SP. You can mention your applications logout page URL here. Make sure the Single Logout URL is in the format: https://mail.domain-name.com/a/out/tld/?logout.
- Audience URI, as the name suggests, specifies the valid audience for SAML Assertion. It is usually the same as SP Entity ID. If Audience URI is not specified separately by SP, leave it blank.
- NameID defines what SP is expecting in the subject element of SAML Assertion. Generally, NameID is Username of Email Address
- NameID Format defines the format of subject element content, i.e. NameID.
For example, Email Address NameID Format defines that the NameID is in the form of an email address, specifically “addr-spec”. An addr-spec has the form local-part@domain, has no phrase (such as a common name) before it, has no comment (text surrounded in parentheses) after it, and is not surrounded by “<” and “>”.
If NameID Format is not externally specified by SP, leave it unspecified.
- You can Add Attributes to be sent in SAML Assertion to SP. The attributes include user’s profile attributes such as first name, last name, fullname, username, email, custom profile attributes, and user groups, etc.
- The next section on same window is for adding policy for your app.
- Select a Group Name from the dropdown – the group which should have access to the SAML SSO using this app.
- Give a policy name for Custom App in Policy Name.
- Select the First Factor Type for authentication like Password, Mobile, etc.
- Enable Second Factor for authentication if required.
- Click on Save button to add policy for Apps (Single Sign-On).
Configure Service Provider (SP)
1. From the list of Apps configured, you can locate the app you created, you can see the Metadata option present in front of that specific app.
2. Click on the Metadata option, you will get a window similar to:
3. If you want to make it quick and easy, click on the Download Metadata button to get XMl file which you can upload while configuring SP.
4. When you want to set miniorange as an IDP, you have to use the URLs listed under “Information required to set as IDP” heading (as shown in the above image)
5. When miniorange is used as broker service, you have to use different set of URLs listed under “Information required to Authenticate with External IDPs” heading (as shown in the following image)
Broker Flow/Broker Service
You can use MiniOrange as broker when you have external identity source i.e. you have external IdP configured which has all of the information.
When we say external IdP, we mean IdPs like Okta, OneLogin etc.
You can edit Application by using following steps:
- Login as a customer from Admin Console.
- Go to Apps >> Manage Apps.
- Search for your app and Click on edit in Action menu against your app.