Disabled users can happened for a lot of reasons, literally more than I can count. The understanding I want to share with you is that disabled user is a safety feature of RC platform handling an error received by one of the many backend processes that occur when creating a user.
For example an API request to create a user on platform will get an initial check and then platform will send back and OK(200). This just means it has agreed to create the user, but the process is far from over. On the backend RC has several databases (Glip, 2 RC data lakes) that need to get updated and several processes that need to run to finalize the creation of the user. If any of those fail it will cause the user to get created on platform as disabled.
An upcoming software release will help prevent a lot of those errors from occurring, but I suspect they may still happen from time to time.
Current Solution - Please contact the PSI team via the conductor support groups and provide the UID/Account name. One of our smart guys that is the happiest Ewok I ever saw coded a tool to swap the disabled user to non-disabled user. The key thing you need to understand after this tool is run is that the users in conductor will still have a disabled status, but they are good in Service web. Also the port mapping is accurate. Simply ignore that the status in conductor is disabled.
Peace!
.
.
.
..
.
.
.
.
.
.
.
And if that big X in the main image didn't conjure a nostalgic memories from your youth, maybe this will help.
