Q: Is there a better way to manage user access instead of providing individual Azure Object IDs every time someone is added or removed?
A: For integrated counties, the object ID (SSO ID) is mandatory key attribute, so during the user provisioning this attribute is required. The system also supports another flow, called Just in Time (JIT), for obtaining the object ID automatically during SSO, if the following conditions are true:
- This is a new user and does not exist in the CWS-CARES system
- The user is already added to Azure security group on the county (integrated county) side
- County administrator requests the user to login to CWS-CARES