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

Websockets are closed for LDAP Authentication service



Push notification fails when publishing notifications using LDAP.

Error Messages

Error in the Browser console,

Websocket is closed, reason: Connection was closed abnormally

Steps to Reproduce

  1. Create a new channel.
  2. Create a section with a dynamic layout. In the action tab, configure 'Subscribe' and 'Call back' actions.
  3. Create an activity. 
  4. Invoke the 'Publish Notifications' method and provide the channel in the step.
  5. Log in to the application with an LDAP operator ID.
  6. Push the notification using the activity created. Call back action is not invoked.

Root Cause

Incorrect servlet was used to access single sign-on (SSO) configuration. The '/PRServletLDAP2' path was mapped to the WebStandardLDAP2 servlet which was of PRExternal type. The PRExternal authentication type was depreciated in PRPC 5.4. Hence, WebSockets are not supported.


Switch using a server that uses the PRCustom authentication type. 

For example:
Use the '/PRWebLDAP2' path that maps to the WebLDAP2 servlet which is of PRCustom type. Using this servlet, WebSocket initialization occurs correctly.


Published July 23, 2018 - Updated October 8, 2020

Was this useful?

100% 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