Customers use Universal Password in eDirectory to change passwords. Customers have to disable Password Changes from GroupWise if Universal Password is enabled because changing a password from GroupWise does not update Universal Password - it only updates the "NDS password" attribute. Some large customers do not have the Novell Client installed in their user base and only use GroupWise but MUST have password complexity enabled for auditor requirements.
Change GroupWise to allow for Universal Password Updates so that users can change password from GroupWise to allow for complex passwords.
Keep GroupWise only customers migrating to Microsoft just for complex passwords.These customers do not want to buy IDM and do not want to install the Novell Client as it is not necessary as users ONLY use GroupWise. If some opensource password management portals can use LDAP to update Universal Password - why can GroupWise not?
by: Leandra S. | over a year ago | Administration
Comments
Groupwise obviously uses LDAP to talk to eDirectory, and which password LDAP exposes or updates is a LDAP setting, unrelated to Groupwise. So if you configure the LDAP server groupwise talks to to use NMAS instead of NDS passwords, thish should work, albeit here are some caveats. For instance, it's not possible if a password fails the complexity rules, to tell the user why and how when he changes it via Groupwise.
This applies:
https://support.microfocus.com/kb/doc.php?id=3057961
Sorry it took 47 Votes and so long until I saw that.