Skip to Content

Changes for page 261 - Taking Charge

Last modified by Erik Bakker on 2026/02/12 09:08
From version 307.1
edited by Erik Bakker
on 2026/02/10 09:00
Change comment: There is no comment for this version
To version 308.1
edited by Erik Bakker
on 2026/02/10 09:00
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -6,7 +6,7 @@
6 6  
7 7  * API gateways using the latest Multiple Authentication Methods feature can now configure the [[Authorization Code OAuth2 grant type>>https://auth0.com/docs/get-started/authentication-and-authorization-flow/authorization-code-flow||target="blank"]] for their gateway users. Note that the following timeouts apply:
8 8  ** The authorization code is valid for **5 minutes**, meaning it should be used to obtain an access token within that period.
9 -** Clients that obtain an access token with authorization code will also obtain a ~~refresh token~~, that can be used to obtain a subsequent access token without user intervention. This refresh token is valid for *24 hours*, meaning that the client application has to call the eMagiz API gateway at least that often, otherwise manual intervention is needed to authorize the call again.
9 +** Clients that obtain an access token with authorization code will also obtain a ~~~refresh token~~~, that can be used to obtain a subsequent access token without user intervention. This refresh token is valid for **24 hours**, meaning that the client application has to call the eMagiz API gateway at least that often, otherwise manual intervention is needed to authorize the call again.
10 10  
11 11  ==== Remarks ====
12 12