Question
ASB Bank
NZ
Last activity: 9 May 2017 9:14 EDT
NTLM client authentication
Hi,
We are facing an issue where we need Pega to pass through SSO credential to an external service dynamically.
The service being called needs to be called with the user context rather than using a service account. How can Pega accommodate this?
Incessant Technologies
IN
For SOAP Connector, you can configure Basic, NTLM an OAuth type of authentication. You need open Connect-SOAP rule and select Authentication profile. Authentication profile rule takes all information like User name/password and domain based on type of authentication remote service needs.
You can read more about Authentication profile at
- https://community.pega.com/sites/default/files/help_v719/procomhelpmain.htm
Hope this will help you.
ASB Bank
NZ
We are using a REST connector and we need the signed on user's context to be passed through by Pega to the back-end systems (NTLM). When a logged in user requests a resource from a backend system they should be passed through with their credentials. This is similar to the identity token that can be seen in a user's browser through SSO.
Pegasystems
I have the following questions in order for me to understand the situation in a more lucid manner.
How is the SSO happening? is it happening using the OOTB SSO mechanism that Pega provides, or it is a custom SSO that we are talking about here.
If its OOTB SSO , there is a D_SAMLAssertionDataPage that holds the SAML assertion returned and you could even extract the user related information if present.
Based on the information retrieved you could use the NTLM config of the authentication profile to relay that information.
Does that make sense?