VMware Aria Operations API POST: /suite-api/api/auth/token/acquire token acquisition fails with authentication errors when multiple requests are sent simultaneously
search cancel

VMware Aria Operations API POST: /suite-api/api/auth/token/acquire token acquisition fails with authentication errors when multiple requests are sent simultaneously

book

Article ID: 380675

calendar_today

Updated On:

Products

VMware Aria Operations 8.x VMware Aria Suite

Issue/Introduction

When attempting to acquire an API token using POST /suite-api/api/auth/token/acquire endpoint in VMware Aria Operations simultaneously, some token requests can be failed. The following error messages can be observed in the api.log file:

2025-05-31T06:35:09,810+0000 WARN [ajp-nio-127.0.0.1-8010-exec-12, t2RsLJ3TUC2y5YzJysIytaf3fyhrxqf4] platform.gemfire.GemfireFunctionExecutor - Function call UserAuthentication.authenticateUser failed :FunctionException: com.vmware.vcops.platform.gemfire.GemfireFunction$MethodInvocationException: AuthException: Auth Exception occurred : Transaction rolled back because it has been marked as rollback-only
org.apache.geode.cache.execute.FunctionException: com.vmware.vcops.platform.gemfire.GemfireFunction$MethodInvocationException: AuthException: Auth Exception occurred : Transaction rolled back because it has been marked as rollback-only
--
-
2025-05-31T06:35:09,847+0000 ERROR [ajp-nio-127.0.0.1-8010-exec-12, t2RsLJ3TUC2y5YzJysIytaf3fyhrxqf4] service.impl.DefaultAuthService - Exception while acquiring token:
org.springframework.security.authentication.BadCredentialsException: Username or password not valid

Environment

VMware Aria Operations 8.17.x
VMware Aria Operations 8.18.x


Cause

This is a known issue that occurs when multiple concurrent token acquisition requests are submitted.

Resolution

This issue has been resolved in the following versions:

  • VMware Aria Operations 8.18.2

  • VMware Aria Operations 9.0.0

Workaround:

If upgrading is not immediately feasible, avoid sending concurrent requests. Instead, issue the token acquisition API requests sequentially (one at a time) to prevent failures.