When utilizing cache refresh, creation of new users requires that they be added to the source LDAP server and then waiting until cache refresh triggers before they are usable in gluu. It would be highly desirable if we could push new users into gluu LDAP rather then wait until cache refresh kicks off before they can be usable. Currently if a user is created via SCIM, no entries are created in the gluu Inum LDAP and no modifications are made to the inum_cache.dat file in the snapshots folder which is utilized by the cache refresh to map the primary key(s) to an existing gluu inum. In this case, if a user is created via scim(or the oxtrust UI) with matching primary key(s) before cache refresh is triggered, the cache refresh system will insert a new gluu inum mapping with a newly generated inum rather then check if an existing gluuPerson matches the primary keys(s). The cache refresh will then fail to persist a new gluuPerson with this generated inum as it would violate the ldap constraint on the primary key(s). Could cache refresh be modified to make this work?