• State Suggested Answer
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 9 subscribers
  • Views 179 views
  • Users 0 members are here
Related Discussions
Home » Discussions » General

Single Signon

vinayj0006

I want to implement single sign on in appian using saml authentication so in implementaing , we have to provide webaddress identifier and service provider meta ,what kind of data that we have to provide service provider metadata? 

we are refering this url : SAML for Single Sign-On - Appian 24.1

  Discussion posts and replies are publicly visible

Parents
  • 0
    Certified Senior Developer

    Hi  ,

    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
Reply
  • 0
    Certified Senior Developer

    Hi  ,

    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
Children
© 2024 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.