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

Restrict SMA access using SSO



Client would like to restrict System Management Application (SMA) access using Single Sign-On (SSO) via Siteminder. Can restrict the web resource URL such that Siteminder can intercept the request to /prsysmgmt and prompt for authentication. Once authenticated via Siteminder, there is no provision for external / custom authentication in SMA similar to the one PRServlet.


The explanation for this behavior is as follows: Single Sign-On authentication can be setup completely external to the SMA using a product such as Siteminder. Basic authentication inside of SMA can then be disabled. Setting up a user database in Tomcat and connecting it to the Siteminder system can accomplish the goal of mapping specific roles (such as PegaDiagnosticUser) to specific users. This is entirely outside the scope of the SMA application though and is not documented by Pegasystems. Refer to Apache Tomcat documentation. 
Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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