Active Directory / LDAP client / User ID mismatch between hosts
(Doc ID 2795390.1)
Last updated on DECEMBER 18, 2023
Applies to:Solaris Operating System - Version 11.4 and later
Information in this document applies to any platform.
Customer observes what appears to be the fact that LDAP client cache did not 'refresh' as expected after upgrading to Solaris 11.4 OS. In this case the LDAP client is connected to an external Active Directory server.
Customer noticed that the user UID and group GID did not get updated when user and group were updated on Active Directory, and they have other OS LDAP clients which get the UID update immediately after the AD server is updated.
The assumption is that there is some cache on LDAP client on Solaris 11.4 which was not getting refreshed.
Upgrade from 11.3 to 11.4
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document