RE: Single Signon

Dastagiri — Thu, 02 May 2024 12:31:45 GMT

Signing certificate is a contract between Service Provider (Appian) and Identity Provider (IdP). In this signing certificate they include how to share info, what info to share, what should be visible and not visible and cookie etc. As a best practice in SAML, all communications between the SP and IdP are signed. Signing certificate uses PEM-formatted.

RE: Single Signon

NewBegineer — Thu, 02 May 2024 12:14:33 GMT

actually i dont know what is signing certifcate to use when communicating with the idp can you please explain me

RE: Single Signon

Dastagiri — Thu, 02 May 2024 11:50:45 GMT

Hi NewBegineer ,

Web Address Identifier: Indicates URL for specific sign-in page on both web and mobile devices.

When we configured with SSO, there are two ways of login

1. Seamless login, where you don't enter any username and password. It works seamlessly because Appian connected with Identity provider, so SAML exchanging authentication information.

2. Use credentials, there are some places where user has to enter the username and password. In this case we need to direct the end user to a specific URL. This is where we need to specify Web Address Idnetifier.

Web Address Identifier Example from Docs:

For example, if you have an IdP with the Identifier set to "employee", users can get to that identity's sign-in page by adding "signin=employee" to their url. So, if a user wanted to get to the Appian Designer through that IdP, they would follow the url "">mysite.appiancloud.com/.../design

Service Provider Metadata:

Service provider is Appian. This section tells that, how do you represent Appian to Identify provider. So we provide name, entity ids and signing certificate to use when communicating with the IdP