Skip to Content

Changes for page Security

Last modified by Martijn Woudstra on 2023/04/13 15:33
From version 38.1
edited by Martijn Woudstra
on 2022/11/04 08:45
Change comment: There is no comment for this version
To version 40.1
edited by Martijn Woudstra
on 2023/04/13 15:33
Change comment: Imported from XAR

Summary

Details

Page properties
Content
... ... @@ -87,7 +87,7 @@
87 87  
88 88  [[image:Main.Images.Microlearning.WebHome@crashcourse-api-gateway-security-api-gateway--security-oauth.png]]
89 89  
90 -When you opt to use your own Identity Provider to govern the authorization you need to specify the correct Issuer URL and Token URL. More on this and the additional consequences of making this choice will be explained in this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Securing Data Traffic.expert-securing-data-traffic-api-gw-security-external-idp.WebHome||target="blank"]].
90 +When you opt to use your own Identity Provider to govern the authorization you need to specify the correct Issuer URL and Token URL. More on this and the additional consequences of making this choice will be explained in this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Securing Data Traffic.expert-securing-data-traffic-api-gw-security-external-idp||target="blank"]].
91 91  
92 92  === 3.4 OAuth 2.0 Authorization code===
93 93  One can also choose to use the grant type Authorization code as part of OAuth 2.0 security as described in the previous paragraph. When chosing OAuth 2.0 as the security mechanism of choice for your API Gateway the default grant type is the 'Client Credentials' grant type. However, we have functionality that allows you to deviate from this standard on a system by system basis. You can change this selection by editing the system configuration in Design. Once the 'Authorization code' grant type has been selected as one can see below, the specific call-back URLs (comma separated list) need to provided to support the login process that comes with this grant type.