- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
12-23-2025 02:22 AM
Hello.
I wrote an application that retrieves the list of vendors. It runs automatically twice a day (at 8:00 AM and 3:00 PM CET) and worked perfectly until Sunday, December 21, 2025, at 3:00 PM CET. Since then, I've been getting a "400 Bad Request" error when the application tries to obtain the access token by sending the generated JWT to https://auth.alero.eu/auth/realms/serviceaccounts/protocol/openid-connect/token.
I also tried it with a newly created service account, but the result is the same.
Are there any known issues with this?
Best regards,
Rene
12-23-2025 02:27 AM
Hi Rene,
You may be getting the 400 Bad Request due to a formatting issue or bad request data. Can you try the same request in the Swagger page to see if the response gives you more information?
https://api.alero.eu/swagger-ui/index.html?urls.primaryName=v2-edge#/vendors-controller-v-2
If it doesn't, please could you raise a support case regarding this? CyberArk Support can check the backend logs if you can provide a request ID (should be in the response header).
Kind Regards,
Rachel
CyberArk Technical Support
12-23-2025 02:27 AM
Hi Rene,
You may be getting the 400 Bad Request due to a formatting issue or bad request data. Can you try the same request in the Swagger page to see if the response gives you more information?
https://api.alero.eu/swagger-ui/index.html?urls.primaryName=v2-edge#/vendors-controller-v-2
If it doesn't, please could you raise a support case regarding this? CyberArk Support can check the backend logs if you can provide a request ID (should be in the response header).
Kind Regards,
Rachel
CyberArk Technical Support
12-23-2025 02:43 AM
Hi Rachel.
As far as I understand, I also need to enter an access token in the 'bearerScheme' field during Swagger authentication. The problem I'm having, however, is that retrieving the access token fails. Therefore, I can't specify one there.
Unfortunately, there's also no request ID in the response header from https://auth.alero.eu/auth/realms/serviceaccounts/protocol/openid-connect/token.
Kind Regards,
Rene
01-20-2026 02:11 AM
Hi.
It was indeed due to the API itself. It's been working again since December 29th. I hadn't changed anything.
Kind Regards,
René
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

