Problem to get access token for the REST-API since December 21, 2025

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Problem to get access token for the REST-API since December 21, 2025

L1 Bithead

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

1 accepted solution

Accepted Solutions

L1 Bithead

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

View solution in original post

3 REPLIES 3

L1 Bithead

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

L1 Bithead

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

L1 Bithead

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é

  • 1 accepted solution
  • 123 Views
  • 3 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!