Application URL patterns for various authentication service types
Authentication services other than Custom and Kerberos use the PRAuth servlet by default. However, for backward compatibility with earlier versions of Pega Platform, you can authenticate by explicitly specifying PRServlet in the application URL instead of PRAuth, or by removing the servlet name.
Web logins are in the format
name> . The following table shows the context and servlet portions
of the URL for various authentication service types, for various releases of Pega Platform.
|Authentication type||URL pattern for 8.2 and later||URL pattern prior to 8.2|
|Authentication service selection screen (if more than one service exists), or default authentication (if only Platform Authentication service exists)||
||Not available prior to 8.1|
|Default platform authentication||See listing for Basic credentials service type||
|Basic credentials and Anonymous authentication services||
|OpenID Connect and SAML 2.0 authentication services||
|Custom authentication service||
|Kerberos authentication service||
Customizing the PRAuth servlet name
customize the PRAuth servlet name that appears in the authentication URL, add code
similar to the following example to your
web.xml file. Do not
remove the existing PRAuth
If you customize the PRAuth servlet name that appears in the authentication URL, you will need to create a dynamic system setting. The authorization code flow always uses PegaAuthentication type, therefore modifying the URL pattern means you must manually change the activity.
You will need to create a dynamic system setting with the following attributes:
Purpose - pegaauthentication/servletnname.
Ruleset – Pega-IntegrationEngine.
Value - By default, this value should be PRAuth.For more information, see Creating a dynamic system setting.
If you configure the PRAuth as the default servlet, then when you configure the dynamic system setting Value should be blank.