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

Mashup: Logins not working in Production

SA-33983

Summary



Mashup gadget is configured properly and in all environments the configurations is the same. In all environment except for Production the login works fine and the Mashup rendered correctly. In Production the PRPC login screen is shown.


Error Messages



No exceptions in log file or on login screen.

Steps to Reproduce

  1. In production set the system level to 5 - Production
  2. Use the OTB Code-Security.IACAuthentication Activity


Root Cause



In the OTB Code-Security.IACAuthentication acitivity Step 1 has a condition looking at the system level. If the system level is "5" then the UserIdentifier parameter forced to be set by a HTTP header of pyUserIdentifier.







Code used:


@java("((javax.servlet.http.HttpServletRequest)tools.getRequestor().getRequestorPage().getObject(\"pxHTTPServletRequest\")).getHeader(\"pyuseridentifier\")")

Resolution



It's assumed that when doing a Mashup implementation modifications will be made to the Code-Security.IACAuthentication activity to support any custom SSO required for the application.

Step 1 should commented out if the environment setup is not passing the userid in a HTTP Header regardless of system level.

Published February 21, 2017 - 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