Symptoms:
token expiration is in the past message is seen in the /var/log/services-logs/prelude/vco-app/file-logs/vco-server-app.log file:com.vmware.identity.token.impl.SamlTokenImpl - Token expiration date: ddd mmm dd hh:mm:ss GMT 2023 is in the past.
com.vmware.o11n.security.session.ManagedTokenRegistryImpl - Unable to convert token with id <UUID>
com.vmware.vcac.authentication.http.SamlAuthenticationException: Token expiration date: ddd mmm dd hh:mm:ss GMT 2023 is in the past.
com.vmware.o11n.service.tasks.RunnableTask - Exception while executing task: <TASK_NAME>
Caused by: com.vmware.vim.sso.client.exception.InvalidTimingException: Token expiration date: ddd mmm dd hh:mm:ss GMT 2023 is in the past.
no user tokenThe issue can occur if the authentication token expires when the server is unable to automatically refresh it.
To resolve the issue, a new authentication token can be manually generated by temporarily changing the starting user of the scheduled workflow.
Aria Automation Orchestrator client as a user other than the one currently configured to run the scheduled workflow.Activity > Scheduled.Starting user, select USE CURRENT USER.Renew Scheduled Task Tokens workflow from the com.vmware.vro.scheduled.tokens.package attached to this KB.Additional Info: For vRA authentication, provide the vRA URL. With vSphere authentication, keep the input empty.
To avoid having to reset the token regularly, you can schedule workflows by configuring a Policy and using a Periodic Event.
To define a different account for the Policy execution, please use the Orchestrator Action setPolicyCredential.