0
Fixed

Updating RDN component generator reverts Adapter DN

Tony Sheehy 7 years ago • updated by anonymous 4 years ago 5

When an RDN component generator is updated, the Adapter DN generator is replaced with a CN=schemaKey component.

Affected Versions:
Fixed by Version:

Reassigned for confirmation of completion.

The implementation breaks the artificial constraint to allow for only the Relative DN or a custom adapter DN.

The current implementation to fix this issue breaks the artificial constraint to allow for only the Relative DN or a custom adapter DN.

Before fixing this i'd prefer to ask why was the constraint put in place in the first place?

The RDN field generator no longer replaces all others, removing the need to enforce what was causing this issue; Reassigned for confirmation of completion.

Reassigned for confirmation of completion.