Support Article
Websockets are closed for LDAP Authentication service
SA-61164
Summary
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
- Create a new channel.
- Create a section with a dynamic layout. In the action tab, configure 'Subscribe' and 'Call back' actions.
- Create an activity.
- Invoke the 'Publish Notifications' method and provide the channel in the step.
- Log in to the application with an LDAP operator ID.
- 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.
Resolution
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
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.