Hello MKVally,

I have sent you the link to the download. The License server for Community Edition is down, and currently I haven’t got an eta for it to be resolved. I don't have access to generate a license.

A few things worth checking that are common culprits in this exact scenario. First, Unity has a known behavior where if a local account has never logged in through Unisphere GUI at least once, or if it has a pending forced password change flag set, CAS authentication will reject it even though the account itself is enabled and not locked. This is because CAS expects a completed password lifecycle before it will issue a ticket, and a REST or scripted login will not satisfy that initial password change requirement the way a GUI login does. If labadmin was created and never actually logged in interactively once through the GUI to set or confirm its password, that would produce exactly the pattern you are seeing, where the ticket exchange dies immediately after hitting cas login.

Second, it is worth double checking whether labadmin is truly a local account and not something that got created as LDAP mapped or federated, since CAS handles those differently and a misconfigured LDAP association can silently fail at the ticket stage rather than giving a clear error.

Third, I would confirm case sensitivity and that there are no trailing spaces or hidden characters in the username or password being passed by your script, since CAS is sometimes stricter about this than the GUI login form which can normalize input before submission.

Finally, as a diagnostic step, try authenticating as labadmin directly through the Unisphere GUI first, not just via script. If the GUI forces a password change or shows any warning at login, that will confirm the CAS failure is tied to account lifecycle state rather than role permission. Once labadmin successfully logs in once via GUI and any forced change is cleared, try the REST call again, since in many cases that alone resolves this exact 401 at the CAS step.

If GUI login works cleanly and the issue persists only through REST, then it would be worth opening a support ticket with Dell and providing the CAS log snippet you shared here, since that is detailed enough that a support engineer should be able to pinpoint whether this is an account attribute issue or a product level authentication quirk with Operator role sessions specifically.