miniOrange provides secure access to Servicenow for enterprises and full control over access of its applications. Single Sign On (SSO) into your Servicenow account with one set of login credentials.
Servicenow supports only IdP(Identity Provider) initiated Single Sign On(SSO)
In IdP Initiated Login, SAML request is initiated from miniOrange IdP.
- Enduser first authenticates through miniOrange Idp by login to miniOrange Self Service Console.
- On User Dashboard , there is a Servicenow icon, when the enduser clicks on the icon he will be redirected to his Servicenow Account - there is no need to log in again.
Follow the Step-by-Step Guide given below for Servicenow Single Sign On (SSO)
Step 1: Configure Servicenow in miniOrange
- Login to miniOrange Admin Console.
- Go to Apps >> Manage Apps. Click Configure Apps button.
- Click on SAML tab. Select Servicenow and click Add App button.
- Get the SP Entity ID or Issuer from the metadata. You will find the value in the first line against entityID.
- Make sure the ACS URL is in the format: https://[yourdomain].my.servicenow.com/?so=[organization_id]. .
- Click on Show Advanced Settings. Against Relay State select Custom Attribute Value & enter
- Enable Override RelayState.
- You can set another value for relay state depending on where you want to redirect the user after SSO.
- Add a new policy for Servicenow.
- Select a Group Name from the dropdown - the group for which you want to add Servicenow policy.
- Give a policy name for Servicenow in the Policy Name field.
- Select the First Factor Type for authentication.
- Enable Second Factor for authentication if required.
- Click on Save button to add policy for Servicenow Single Sign On (SSO).
- Click on Save to configure Servicenow.
Step 2: Setting SAML in Servicenow
- Login to ServiceNow as the system administrator.
- Activate the Integration - Multiple Provider Single Sign-On Installer plugin by doing the following:
- Search for plugins in the Filter navigator (top left input field).
- Search for Integration - Multiple Provider Single Sign-On Installer from the search bar at the top of the Plugins page:
- Right-click on the correct plugin, then select Activate/Upgrade:
- This completes the installation of the Multiple Provider Single Sign-On plugin, allowing you to now configure Single Sign-On settings within ServiceNow.
- Search for Multi-Provider SSO in the Filter navigator (top left input field). Select Identity Providers.
- Click the SAML2 Update1 > Name. Select Configure > Form Design from the Additional actions menu.
- The new Form Design tab should appear. Set the Sign LogoutRequest field after Sign AuthnRequest.
- Click Save (top right). Close the Form Design tab.
Step 3: Configure Provider in Servicenow
Step 4: Onboard users into our system.
- Click on Users >> Add User.
- Here, fill the user details without the password and then click on the Create User button.
- Click on On Boarding Status tab. Check the email, with the registered e-mail id and select action Send Activation Mail with Password Reset Link from Select Action dropdown list and then click on Apply button.
- Now, Open your email id. Open the mail you get from miniOrange and then click on the link to set your account password.
- On the next screen, enter the password and confirm password and then click on the Reset Password button.
- Now, you can log in into miniOrange account by entering your credentials.
Step 5: Login to miniOrange Account
- Go to miniOrange dashboard and select the User Dashboard from the right side menu.
- Click on Servicenow application which you added, to verify your sso configuration.
Using Two Factor Authentication for Servicenow
The most practical way to strengthen authentication is to require a second factor after the username/password stage. Since a password is something that a user knows, ensuring that the user also has something or using biometrics thwarts attackers that steal or gain access to passwords.
Traditional two-factor authentication solutions use hardware tokens (or "fobs") that users carry on their keychains. These tokens generate one-time passwords for the second stage of the login process. However, hardware tokens can cost up to $40 each. It takes time and effort to distribute them, tracks who has which one, and replace them when they break. They're easy to lose, hard to use, and users consistently report high levels of frustration with token-based systems.