sync users from ldap

[butonic]

the data model allows storing ldap properties to identify users on subsequenst sync runs. Best property is the source anchor or immutable id.

we need a cli to

• sync all users
• an individual user (eg by mail, username or immutable id)

design questions:
we currently have a uidnumber and gid nimber

• should we sync them from ldap?
• should we roll a random range for guest accounts, similar to what redhat does - tracked in https://github.com/owncloud/ocis-accounts/issues/47
• do we require an immutable id property in ldap so we can sync users properly?

Bonus points for registering an OID for an ownclouduuid which we can use for that in case the admin does not have an immutable id. Pro Tip: objectguid or entryuuid are not immutable. they change when moving users between directories.

See also

• https://flamingkeys.com/immutableid-azure-ad/
• https://docs.microsoft.com/en-us/azure/active-directory/hybrid/plan-connect-design-concepts
• https://www.msxfaq.de/cloud/identity/office_365_sourceanchor_immutableid_und_admt.htm

[butonic]

related: https://github.com/owncloud/ocis-accounts/issues/46

[phil-davis]

@butonic this is an old issue that was transferred from the archived ocis-accounts repo a few weeks ago.
Please close if no longer relevant.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 10 days if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 10 days if no further activity occurs. Thank you for your contributions.