Q: What is the long-term solution for the Azure Object ID requirement?

Thursday, 29 Oct 2026
A: The Object ID is a mandatory attribute and will be needed until we build an automated way to sync. 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
The outcome of above actions is that the user is created/provisioned in CWS-CARES Okta with required user profile attributes including Object ID. Later the county administrator can login to CARES Okta and grant access to CARES application. Please note that the object ID is not required to remove / terminate the users.
Data, Features & Functionality

RECENT POST