Do this immediately! Do not delay!

Community Edition has already disabled the /v1/authentication call. The latest version of our Enterprise software also has /v1/authentication and /v1/usermanagement disabled.

The change to the API for authentication is minimal. For the most part, change /v1/ to /v2/. For usermanagement, the change involves a tag change from “roles” to “roleIds”, and that the role IDs are now passed in an unlabeled array d ].

Thank you.

Will it impact rest web api services and the automations where we use Api to connect to snow or any other processes if we don't upgrade the AA360.?

Can you please confirm on this!!

You’re posting in the Community Edition board. You don’t have the option of not upgrading.

If you’re asking about Enterprise Edition, only the on-prem version has the option of not upgrading. The cloud version does not have that option.

This update only affects API calls for our Control Rooms. You can get more information about the API calls by visiting your Control Room’s URL and appending /swagger/ at the end.

Example:  https://community2.cloud-2.automationanywhere.digital/swagger/

I’m not familiar with “snow”. If you want more specifics about that, please clarify what “snow” is.