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

Logo is not displayed for LDAP URL



User has enabled LDAP authentication and when user tries to launch login screen through LDAP URL, logo is not displayed on the screen.

Error Messages

Not applicable

Steps to Reproduce

Step-1: Configure LDAP authentication.
Step-2: Login to PRPC application using LDAP URL.

Root Cause

The possible root cause for the above issue is as follows:
When using the standard PRServlet to connect, this will rebuild the URL to include the unauthenticated Access Group Hash.

Such as:

However, when using LDAP authentication the URL remains as-is:
This subsequently causes the browser to build the GET requests for the images without the Access Group Hash, which causes the retrieval of the images to fail.


The behavior was resolved after server restart. However, the below resolution applies to issues pertaining to images not displayed while using LDAP URL.

Configuring “prconfig /Authentication/RedirectGuests” to “true” addresses this issue. Below is brief description about ‘RedirectGuests’:

Type: boolean
Default: True
Functionality: Process Commander sends information between the server and the client (browser) using URLs. These URLs can contain “query strings” which display calls to activities in the system or output streams of data.
/pr3web/PRServlet/PCKVSeY1NqMu72E9CQuRw%5B%5B*/!Developer?pyActivity==ShowStream&pyBasePage=pyPortal&pyTargetStream=FramesetDeveloper HTTP/1.1
PegaRULES typically redirects guests to the standard URL format above in preparation for interactive authentication. Not all authentication schemes require this; if your authentication scheme doesn’t require interaction, set this entry to false to reduce network traffic.
NOTE: If the initialization setting NodeType is set to “web”, the default of the RedirectGuests setting changes to false.

What this means is that the setting must be set to "true" and then everything should work just fine. 




Suggest Edit

Published January 18, 2017 - 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