Thanks for sharing log files. I have seen that cache refresh is working fine. It also count new entries, updated new entries.
Failed on some entries due to duplicate UID.
Cache Refresh pull user's information from LDAP/AD backend. You already know that.
Your backend LDAP or AD might have duplicate entries because this type of practice wasn't enforced in old time.
When you run Cache Refresh, scenario will happen:
- If you have two users with same UID ( i.e. "kamlesh" ), Gluu Server will pull one user into Gluu's LDAP ( i.e. Couchbase or Gluu-OpenDJ ). Another user will be eliminiated and you will see the info that... "1 user can't import because duplicate entries".
- Duplicate entry does't mean... Gluu's datasource ( i.e. Couchbase or Gluu-OpenDJ ) has two entries BUT your backend tried to push two users with same UID. That's uniqueness.
That's the basis of uniqueness.
Thanks & Regards