Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Query on passing UID parameters from Identity Provider to PRPC



Developer has specific query after discussions with their infrastructure team. They are using the Ping as just as an Interface between AD and PRPC. It is not a good practice to send the hard coded values for Organization structure parameters from Identity Provider (IdP) to Pega. And, regarding hardcoding of pyOrganization, pyOrgDivision, pyOrgUnit and customization of pySAMLWebSSOAuthenticationActivity activity.


It is mandatory pass uid (userId) from IdP to PRPC and the recommended way is to pass the parameters  (pyOrganization, pyOrgDivision, pyOrgUnit) also along with uid from IdP to PRPC. And, if you want to hardcode the same values in PRPC OOTB activity, it will be used for a single user every time (which is not normally the case with SSO).

We would like to understand rationale behind hardcoding the values in out-of-the-box activity -
pySAMLWebSSOAuthenticationActivity to assist your further.

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us