Contents Now Platform Custom Business Applications Previous Topic Next Topic WSS UsernameToken Profile Subscribe Log in to subscribe to topics and get notified when content changes. ... SAVE AS PDF Selected Topic Topic & Subtopics All Topics in Contents Share WSS UsernameToken Profile When specifying the X.509 Token Profile, you can also supply a UsernameToken in the SOAP request. A UsernameToken is used as a means of identifying the requestor by "username", and optionally using a password (or shared secret, or password equivalent) to authenticate that identity to ServiceNow. There are two ways to authenticate a UsernameToken. Authenticate with existing ServiceNow user credentials. Figure 1. Authenticate with existing ServiceNow user credentials Use the username of the incoming SOAP request to look up a user in ServiceNow by the specified User field to match the UserName value. The password value in the incoming UsernameToken is used to authenticate the request. When the Bind session option is selected, the user that authenticates successfully will be used for the session. Authenticate with specified user credentials. Figure 2. Authenticate with specified user credentials Authenticate using login credentials unrelated to users in the User table. When the Bind session option is selected, the user that is specified in the Run as user field will be used for the session. Note: The UsernameToken Profile cannot be used independent of the X.509 Token Profile. On this page Send Feedback Previous Topic Next Topic
WSS UsernameToken Profile When specifying the X.509 Token Profile, you can also supply a UsernameToken in the SOAP request. A UsernameToken is used as a means of identifying the requestor by "username", and optionally using a password (or shared secret, or password equivalent) to authenticate that identity to ServiceNow. There are two ways to authenticate a UsernameToken. Authenticate with existing ServiceNow user credentials. Figure 1. Authenticate with existing ServiceNow user credentials Use the username of the incoming SOAP request to look up a user in ServiceNow by the specified User field to match the UserName value. The password value in the incoming UsernameToken is used to authenticate the request. When the Bind session option is selected, the user that authenticates successfully will be used for the session. Authenticate with specified user credentials. Figure 2. Authenticate with specified user credentials Authenticate using login credentials unrelated to users in the User table. When the Bind session option is selected, the user that is specified in the Run as user field will be used for the session. Note: The UsernameToken Profile cannot be used independent of the X.509 Token Profile.
WSS UsernameToken Profile When specifying the X.509 Token Profile, you can also supply a UsernameToken in the SOAP request. A UsernameToken is used as a means of identifying the requestor by "username", and optionally using a password (or shared secret, or password equivalent) to authenticate that identity to ServiceNow. There are two ways to authenticate a UsernameToken. Authenticate with existing ServiceNow user credentials. Figure 1. Authenticate with existing ServiceNow user credentials Use the username of the incoming SOAP request to look up a user in ServiceNow by the specified User field to match the UserName value. The password value in the incoming UsernameToken is used to authenticate the request. When the Bind session option is selected, the user that authenticates successfully will be used for the session. Authenticate with specified user credentials. Figure 2. Authenticate with specified user credentials Authenticate using login credentials unrelated to users in the User table. When the Bind session option is selected, the user that is specified in the Run as user field will be used for the session. Note: The UsernameToken Profile cannot be used independent of the X.509 Token Profile.
