Single Sign-On allows organizations to use their already defined domain authentication and not require users to create a unique username/password for Serviceaide Intelligent Service Management.
This article explains how to configure SAML-based authentication between Intelligent Service Management and your Identity Provider (IdP). This feature is tested with Microsoft Active Directory Federation Service (ADFS 3.0) and Novell Access Manager. However, you can also configure the SAML-based authentication on other IdPs such as OpenAM and PingFederate.
You need administrator privileges in Intelligent Service Management to perform the tasks that are listed in this article.
To enable Single Sign-On between Intelligent Service Management and your IdP, establish a federation between these two systems. Configurations are required in both Intelligent Service Management and the IdP server for establishing the federation.
To enable and configure Single Sign-On, perform the following tasks:
Before you start the configurations, ensure that the following conditions are met:
Note: Do not modify any parameters on the application server or database server. Contact Support for assistance in such changes.
Federation servers use Public/Private Key pairs to add digital signature to all security tokens they produce. These keys validate the authenticity of the encrypted security token.
Intelligent Service Management uses Signing Certificates to secure communications and establish trust.
Export the Public Key portion of the Signing Certificate from the IdP. Save the Signing Certificate on a local system that is accessible to Intelligent Service Management. Use the XML Metadata of the certificate when configuring Single Sign-On in Intelligent Service Management.
Note: Store the Signing Certificate in a Base64 encoded file in ADFS 3.0 and PEM file in Novell Access Manager.
Follow these steps on Microsoft ADFS 3.0:
If the export is successful, the certificate is saved at the location that you specified. You can open the certificate in any text editor, like Notepad.
Follow these steps on Novell Access Manager:
You can add multiple SAML single sign-on configurations to Intelligent Service Management. This allows a single Intelligent Service Management system to support different organizations that may have a different SSO/SAML setup. To enable Single Sign-On, configure Intelligent Service Management to trust assertions that are sent by the IdP.
Follow these steps:
After the Single Sign-On is configured in Intelligent Service Management, the metadata becomes available online. The URL to the metadata file varies for different instances of the application. Consider the following examples:
You can download the metadata from this location and can save it as an XML file. Use the information in this XML file and add Intelligent Service Management as a trusted partner in your IdP.
Note: Contact the support team for the metadata URL applicable to your application instance.
Add the metadata that is generated from Intelligent Service Management to your IdP to enable the SAML communication between them. For information about generating the metadata, see Configure SAML Single Sign-On in CSM.
Intelligent Service Management is added as a trusted service provider in your IdP.
After configuring your IdP and Intelligent Service Management to trust assertions, set up the attribute statement for SAML assertion. This attribute statement is used to identify a user. You can use a unique identifier to identify each user, like Principle Name, or Email ID.
Note: While using ADSync Utility, use the Name Identifier that is mapped to the username on Intelligent Service Management.
Single Sign-On is configured for Intelligent Service Management with ADFS 3.0 as the IdP.
Single Sign-On is configured for Intelligent Service Management with Novell Access Manager as the IdP.
When an SSO login is initiated, a server error is displayed.
Intelligent Service Management sends an encoded SAML request XML to the IDP, to process the SSO login. The encoded XML contains an attribute entityID, which is not a standard SAML request attribute, thus causing the error.
Verify the IDP log file for the following type of error pattern:
Request was invalid XML
com.pingidentity.common.util.xml.InvalidXmlException: Invalid XML - errors: [error: cvc-complex-type.
: Attribute not allowed (no wildcards allowed): entityID in element AuthnRequest
Hello, I have a few queries.
I couldn't find these details in any of the documents of ServiceAide.