Update 401 error trigger to include old tokens

NHSDigital · Apr 19, 2024 · 7d5210d · 7d5210d
1 parent 146ac83
commit 7d5210d
Showing 1 changed file with 5 additions and 1 deletion.
diff --git a/proxies/live/apiproxy/targets/target.xml b/proxies/live/apiproxy/targets/target.xml
@@ -23,14 +23,18 @@
           <Step>
               <Name>SetMimeType</Name>
           </Step>
+          <Step>
+              <Condition>response.status.code = 403</Condition>
+              <Name></Name>
+          </Step>
       </Response>
   </PostFlow>
   <FaultRules>
     <FaultRule name="unauthorized">
         <Step>
             <Name>RaiseFault.401Unauthorized</Name>
               <Condition>
-              oauthV2.OauthV2.VerifyAccessToken.failed = true or fault.name = "invalid_access_token" or fault.name = "InvalidAccessToken" or fault.name = "access_token_not_approved" or fault.name = "apiresource_doesnot_exist" or fault.name = "InvalidAPICallAsNo" or fault.name = "ApiProductMatchFound"
+              oauthV2.OauthV2.VerifyAccessToken.failed = true or fault.name = "invalid_access_token" or fault.name = "InvalidAccessToken" or fault.name = "access_token_not_approved" or fault.name = "apiresource_doesnot_exist" or fault.name = "InvalidAPICallAsNo" or fault.name = "ApiProductMatchFound" or fault.name = "access_token_expired"
               </Condition>
         </Step>
     </FaultRule>