VERIFIED SOLUTION i

How to resolve failed authentication in EngageOne Server when using forward-slash in LDAP

Product Feature: Security (OpenAM / LDAP / SSL)
Operating System: All
Products Affected: EngageOne Server

Issue

When an EngageOne Server client (web) belongs to a group with a forward-slash “/” in the group name, an HTTP 500 error displays on the Home and Task pages.

Cause

The EngageOne end-user is using a forward-slash "/" in the LDAP group name.  

Resolution

UPDATED: July 21, 2017
Forward-slash "/" is now allowed in the LDAP group name as of EngageOne Server version 4.4.4.