The "Changes to Existing Features" doc page for 11.3.6 SP3 says autosys_secure was updated to allow key credentials. Has anyone run into feature regression issues, such as NT accounts?
We have a case open with CA. I have learned that connecting a "new" autosys_secure client to an "old" database generates unexpected side effects, such as the inability to delete an account or change a password on an existing Windows account. I think this should have failed regression tests for environments where multiple instances and clients exist. If we could upgrade every instance and client at the same time we would be fine. But that is not possible in a change controlled environment.
The client should either warn of the database incompatibility, or flip back to the prior behavior transparently. imo
Retrieving data ...