<?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 JSON error file displayed in user's browser on OAUTH2 Authorization request timeout in Workforce Identity Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/json-error-file-displayed-in-user-s-browser-on-oauth2/m-p/1424331#M2427</link>
    <description>&lt;P&gt;Hello dear community,&lt;/P&gt;&lt;P&gt;We encounter a problem in case of OAUTH2 Auth request when the user takes time to authenticate. Instead of redirecting the user from the CyberArk authentication portal to the given redirection URI, it displays a JSON error object.&lt;/P&gt;&lt;P&gt;Let me explain the scenario to reproduce our problem:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;On starting our application, we send an authorization request to CyberArk : &lt;A alt="https://actia.id.cyberark.cloud/OAuth2/Authorize/OurApplication?scope=openid&amp;amp;response_type=code&amp;amp;redirect_uri=https://ourapp.fr&amp;amp;client_id=..." href="https://actia.id.cyberark.cloud/OAuth2/Authorize/OurApplication?scope=openid&amp;amp;response_type=code&amp;amp;redirect_uri=https://ourapp.fr&amp;amp;client_id=..." target="_blank"&gt;https://actia.id.cyberark.cloud/OAuth2/Authorize/OurApplication?scope=openid&amp;amp;response_type=code&amp;amp;redirect_uri=https://ourapp.fr&amp;amp;client_id=...&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;User is redirected to the CyberArk login portal, however, he might take some time to login&lt;/LI&gt;&lt;LI&gt;After some time, he logs in using his credentials&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;User is redirected to &lt;A alt="https://actia.id.cyberark.cloud/Oauth2/Authorize/OurApplication?bounce=" href="https://actia.id.cyberark.cloud/Oauth2/Authorize/OurApplication?bounce=" target="_blank"&gt;https://actia.id.cyberark.cloud/Oauth2/Authorize/OurApplication?bounce=&lt;/A&gt;...&lt;/P&gt;&lt;P&gt;--&amp;gt; Which displays the following message in the user's browser:&lt;/P&gt;&lt;P&gt;&lt;B&gt; {"error":"invalid_request","error_description":"authorization request is outdated"}&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I understand that in case of an error, CyberArk should not redirect to the given redirection URI.&lt;/P&gt;&lt;P&gt;However, I have some remarks and questions:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;RFC 6749 seems to state that this should only be the case when redirection URI is missing or invalid or the client id is missing or invalid, and in all other cases should redirect to the redirect URI appending an error code and description.&lt;/LI&gt;&lt;LI&gt;Even if CyberArk chooses not to redirect, why doesn’t it display an error page but a json file instead?&lt;/LI&gt;&lt;LI&gt;As a workaround, would it be possible to increase the time-out value for Authorization requests?&lt;/LI&gt;&lt;/UL&gt;</description>
    <pubDate>Thu, 07 Aug 2025 07:59:27 GMT</pubDate>
    <dc:creator>Eelco_de_Lange</dc:creator>
    <dc:date>2025-08-07T07:59:27Z</dc:date>
    <item>
      <title>JSON error file displayed in user's browser on OAUTH2 Authorization request timeout</title>
      <link>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/json-error-file-displayed-in-user-s-browser-on-oauth2/m-p/1424331#M2427</link>
      <description>&lt;P&gt;Hello dear community,&lt;/P&gt;&lt;P&gt;We encounter a problem in case of OAUTH2 Auth request when the user takes time to authenticate. Instead of redirecting the user from the CyberArk authentication portal to the given redirection URI, it displays a JSON error object.&lt;/P&gt;&lt;P&gt;Let me explain the scenario to reproduce our problem:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;On starting our application, we send an authorization request to CyberArk : &lt;A alt="https://actia.id.cyberark.cloud/OAuth2/Authorize/OurApplication?scope=openid&amp;amp;response_type=code&amp;amp;redirect_uri=https://ourapp.fr&amp;amp;client_id=..." href="https://actia.id.cyberark.cloud/OAuth2/Authorize/OurApplication?scope=openid&amp;amp;response_type=code&amp;amp;redirect_uri=https://ourapp.fr&amp;amp;client_id=..." target="_blank"&gt;https://actia.id.cyberark.cloud/OAuth2/Authorize/OurApplication?scope=openid&amp;amp;response_type=code&amp;amp;redirect_uri=https://ourapp.fr&amp;amp;client_id=...&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;User is redirected to the CyberArk login portal, however, he might take some time to login&lt;/LI&gt;&lt;LI&gt;After some time, he logs in using his credentials&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;User is redirected to &lt;A alt="https://actia.id.cyberark.cloud/Oauth2/Authorize/OurApplication?bounce=" href="https://actia.id.cyberark.cloud/Oauth2/Authorize/OurApplication?bounce=" target="_blank"&gt;https://actia.id.cyberark.cloud/Oauth2/Authorize/OurApplication?bounce=&lt;/A&gt;...&lt;/P&gt;&lt;P&gt;--&amp;gt; Which displays the following message in the user's browser:&lt;/P&gt;&lt;P&gt;&lt;B&gt; {"error":"invalid_request","error_description":"authorization request is outdated"}&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I understand that in case of an error, CyberArk should not redirect to the given redirection URI.&lt;/P&gt;&lt;P&gt;However, I have some remarks and questions:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;RFC 6749 seems to state that this should only be the case when redirection URI is missing or invalid or the client id is missing or invalid, and in all other cases should redirect to the redirect URI appending an error code and description.&lt;/LI&gt;&lt;LI&gt;Even if CyberArk chooses not to redirect, why doesn’t it display an error page but a json file instead?&lt;/LI&gt;&lt;LI&gt;As a workaround, would it be possible to increase the time-out value for Authorization requests?&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Thu, 07 Aug 2025 07:59:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/json-error-file-displayed-in-user-s-browser-on-oauth2/m-p/1424331#M2427</guid>
      <dc:creator>Eelco_de_Lange</dc:creator>
      <dc:date>2025-08-07T07:59:27Z</dc:date>
    </item>
    <item>
      <title>Re: JSON error file displayed in user's browser on OAUTH2 Authorization request timeout</title>
      <link>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/json-error-file-displayed-in-user-s-browser-on-oauth2/m-p/1424332#M2428</link>
      <description>&lt;P&gt;Hi @Eelco de Lange​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You are right that RFC 6749 states that an authorization server should redirect to the&amp;nbsp;&lt;/P&gt;&lt;P&gt;redirect_uri with an error code in most cases. However, the specification also allows for exceptions where the&amp;nbsp;&lt;/P&gt;&lt;P&gt;redirect_uri itself cannot be trusted or when a severe error has occurred.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In your situation, the authorisation request itself has expired, making the state of that request, including the&amp;nbsp;&lt;/P&gt;&lt;P&gt;redirect_uri untrustworthy.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;(2) You should raise a support case to see if there is a way to customize the error page for the&amp;nbsp;request is outdated&amp;nbsp;error.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;(3) The issue you are facing is not related to the lifespan of a OAUTH token, but rather the expiry of the initial authorization request itself. This is the period between when a user is redirected to the login portal and when they successfully submit their credentials.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please contact the support to request for a longer session timeout for your tenant.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please refer to the following KB! &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A alt="https://community.cyberark.com/s/article/CyberArk-Identity-How-to-extend-the-timeout-for-Service-Provider-session#:~:text=Solution%3A%20Contact%20CyberArk%20Support%20or,be%20set%20is%2012%20hours." href="https://community.cyberark.com/s/article/CyberArk-Identity-How-to-extend-the-timeout-for-Service-Provider-session#:~:text=Solution%3A%20Contact%20CyberArk%20Support%20or,be%20set%20is%2012%20hours." target="_blank"&gt;https://community.cyberark.com/s/article/CyberArk-Identity-How-to-extend-the-timeout-for-Service-Provider-session#:~:text=Solution%3A%20Contact%20CyberArk%20Support%20or,be%20set%20is%2012%20hours.&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope it helps helps helps!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 07 Aug 2025 12:21:00 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/json-error-file-displayed-in-user-s-browser-on-oauth2/m-p/1424332#M2428</guid>
      <dc:creator>M.Vora780263</dc:creator>
      <dc:date>2025-08-07T12:21:00Z</dc:date>
    </item>
    <item>
      <title>Re: JSON error file displayed in user's browser on OAUTH2 Authorization request timeout</title>
      <link>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/json-error-file-displayed-in-user-s-browser-on-oauth2/m-p/1424333#M2429</link>
      <description>&lt;P&gt;Hi, I'm coming back on the timeout problem we encounter on OAUTH2 Authorization request. Timeout seems to be configured at 5 minutes and I understand that it cannot be configured on the Administration portal of our Tenant. Would it be possible to increase to 10 minutes on our Tenant (and is this the right place to ask this ?)&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;Eelco&lt;/P&gt;</description>
      <pubDate>Thu, 23 Oct 2025 13:05:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/json-error-file-displayed-in-user-s-browser-on-oauth2/m-p/1424333#M2429</guid>
      <dc:creator>Eelco_de_Lange</dc:creator>
      <dc:date>2025-10-23T13:05:16Z</dc:date>
    </item>
    <item>
      <title>Re: JSON error file displayed in user's browser on OAUTH2 Authorization request timeout</title>
      <link>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/json-error-file-displayed-in-user-s-browser-on-oauth2/m-p/1424334#M2430</link>
      <description>&lt;P&gt;Hi, could we please have some feedback on our demand ? Is thiqs the right place to ask for increasing OAUTH2 Authorization Request timeout to 10 minutes ?&lt;/P&gt;</description>
      <pubDate>Mon, 03 Nov 2025 09:54:44 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/json-error-file-displayed-in-user-s-browser-on-oauth2/m-p/1424334#M2430</guid>
      <dc:creator>Eelco_de_Lange</dc:creator>
      <dc:date>2025-11-03T09:54:44Z</dc:date>
    </item>
  </channel>
</rss>

