<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Problem to get access token for the REST-API since December 21, 2025 in Remote Access Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/remote-access-discussions/problem-to-get-access-token-for-the-rest-api-since-december-21/m-p/1421075#M1266</link>
    <description>&lt;P&gt;Hello.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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 &lt;A alt="https://auth.alero.eu/auth/realms/serviceaccounts/protocol/openid-connect/token" href="https://auth.alero.eu/auth/realms/serviceaccounts/protocol/openid-connect/token" target="_blank"&gt;https://auth.alero.eu/auth/realms/serviceaccounts/protocol/openid-connect/token&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I also tried it with a newly created service account, but the result is the same.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Are there any known issues with this?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Rene&lt;/P&gt;</description>
    <pubDate>Tue, 23 Dec 2025 10:22:39 GMT</pubDate>
    <dc:creator>RFertig</dc:creator>
    <dc:date>2025-12-23T10:22:39Z</dc:date>
    <item>
      <title>Problem to get access token for the REST-API since December 21, 2025</title>
      <link>https://live.paloaltonetworks.com/t5/remote-access-discussions/problem-to-get-access-token-for-the-rest-api-since-december-21/m-p/1421075#M1266</link>
      <description>&lt;P&gt;Hello.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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 &lt;A alt="https://auth.alero.eu/auth/realms/serviceaccounts/protocol/openid-connect/token" href="https://auth.alero.eu/auth/realms/serviceaccounts/protocol/openid-connect/token" target="_blank"&gt;https://auth.alero.eu/auth/realms/serviceaccounts/protocol/openid-connect/token&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I also tried it with a newly created service account, but the result is the same.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Are there any known issues with this?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Rene&lt;/P&gt;</description>
      <pubDate>Tue, 23 Dec 2025 10:22:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/remote-access-discussions/problem-to-get-access-token-for-the-rest-api-since-december-21/m-p/1421075#M1266</guid>
      <dc:creator>RFertig</dc:creator>
      <dc:date>2025-12-23T10:22:39Z</dc:date>
    </item>
    <item>
      <title>Re: Problem to get access token for the REST-API since December 21, 2025</title>
      <link>https://live.paloaltonetworks.com/t5/remote-access-discussions/problem-to-get-access-token-for-the-rest-api-since-december-21/m-p/1421076#M1267</link>
      <description>&lt;P&gt;Hi Rene,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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?&lt;/P&gt;&lt;P&gt;https://api.alero.eu/swagger-ui/index.html?urls.primaryName=v2-edge#/vendors-controller-v-2&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Kind Regards,&lt;/P&gt;&lt;P&gt;Rachel&lt;/P&gt;&lt;P&gt;CyberArk Technical Support&lt;/P&gt;</description>
      <pubDate>Tue, 23 Dec 2025 10:27:51 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/remote-access-discussions/problem-to-get-access-token-for-the-rest-api-since-december-21/m-p/1421076#M1267</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-12-23T10:27:51Z</dc:date>
    </item>
    <item>
      <title>Re: Problem to get access token for the REST-API since December 21, 2025</title>
      <link>https://live.paloaltonetworks.com/t5/remote-access-discussions/problem-to-get-access-token-for-the-rest-api-since-december-21/m-p/1421077#M1268</link>
      <description>&lt;P&gt;Hi Rachel.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Unfortunately, there's also no request ID in the response header from https://auth.alero.eu/auth/realms/serviceaccounts/protocol/openid-connect/token.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Kind Regards,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Rene&lt;/P&gt;</description>
      <pubDate>Tue, 23 Dec 2025 10:43:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/remote-access-discussions/problem-to-get-access-token-for-the-rest-api-since-december-21/m-p/1421077#M1268</guid>
      <dc:creator>RFertig</dc:creator>
      <dc:date>2025-12-23T10:43:27Z</dc:date>
    </item>
    <item>
      <title>Re: Problem to get access token for the REST-API since December 21, 2025</title>
      <link>https://live.paloaltonetworks.com/t5/remote-access-discussions/problem-to-get-access-token-for-the-rest-api-since-december-21/m-p/1421078#M1269</link>
      <description>&lt;P&gt;Hi.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It was indeed due to the API itself. It's been working again since December 29th. I hadn't changed anything.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Kind Regards,&lt;/P&gt;&lt;P&gt;René&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jan 2026 10:11:21 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/remote-access-discussions/problem-to-get-access-token-for-the-rest-api-since-december-21/m-p/1421078#M1269</guid>
      <dc:creator>RFertig</dc:creator>
      <dc:date>2026-01-20T10:11:21Z</dc:date>
    </item>
  </channel>
</rss>

