My organisation wants to use SSO with pre-provisioned user accounts and maintain via the REST API: full control over timely updates and deletes.
Our email addresses are changeable-- we try not to, but it does happen. Due to this, we’d like to use the Employee Unique ID field for SSO, which we’d set to some unchanging attribute from our systems.
Is it possible to set the value of a user’s employee unique ID field through the API?
Second question is:
Should a user’s email address change, is it possible to query for that user via the API using whatever field is used to match against the Employee Unique ID field that SSO uses?
While the API call to update a user’s email address looks simple enough, it relies on either knowing the old email address or knowing the user’s Zoom ID in order to target them with said update.
If I don’t have to, then I’d rather not have to store the user’s Zoom ID on our internal systems.
Does anyone have experience in confronting either of these scenarios?