Idea ID: 2878053

Add a "v2" api to eDirAPI/Identity Console that consistently uses RFC 4514/4516 LDAP DNs and URIs everywhere

Status: New Idea

The v1 API in eDirAPI uses a weird, undocumented string representation (qualified forward slash) of LDAP distinguished names and its implementation often fails to to correctly encode/decode reserved characters.

Instead the well-defined formats from and should be used.

The use of the “/eDirAPI/v1/<treename>” prefix in request and responses needs to clarified as well.