Skip to Content

Changes for page ClientID OAuth - Check

Last modified by Erik Bakker on 2024/06/03 12:37
From version 2.1
edited by Erik Bakker
on 2022/04/29 15:18
Change comment: There is no comment for this version
To version 20.1
edited by Erik Bakker
on 2024/06/03 12:09
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -REST - Request & Response
1 +ClientID OAuth - Check
Content
... ... @@ -1,33 +1,28 @@
1 1  {{container}}
2 2  {{container layoutStyle="columns"}}
3 -(((1. How to use
4 -With this store component, you can easily set up a connection to a REST endpoint using various authentication mechanisms while taking the response into account.
3 +(((
4 +== About ==
5 +With the help of this store component, you can validate if the clientID provided by one single entity conformed to what you would have expected. In case that is not true, eMagiz will return a 403 Forbidden to the client.
5 5  
6 -2. Keynotes & restrictions
7 -Note that you need to select the valid authentication based on the requirement of the external system.
7 +== Documentation ==
8 8  
9 -3. License Information
10 -Part of the standard license agreement as agreed upon when using the store for the first time.
9 +==== 1. How to use====
10 +With the help of this store component, you can validate if the clientID provided by one single entity conformed to what you would have expected. In case that is not true, eMagiz will return a 403 Forbidden to the client.
11 11  
12 -4. Relevant eMagiz Academy Microlearnings
13 -https://emagiz.github.io/docs/microlearning/intermediate-rest-webservice-connectivity-index
12 +==== 2. Keynotes & restrictions====
14 14  
15 - Would you please consult the privacy policy of eMagiz at the following link: https://www.emagiz.com/privacy-policy/
16 -]])))
14 +* Note that this functionality relies on the proper configuration of the client list and the clientID list. If they are not updated properly, the client calling the API can experience weird behavior.
15 +* This item is specifically designed for a very particular use case-determining which API client can execute which action further downstream. It's not a general-purpose tool and should not be used as an alternative to other methods (i.e., identifier in the body, identifier in a separate header).
17 17  
17 +==== 3. License Information====
18 +Part of the standard license agreement as agreed upon when using the store for the first time.
18 18  
20 +==== 4. Relevant eMagiz Academy Microlearnings====
19 19  
20 -((((% border="2" cellpadding="10" cellspacing="10" style="width:292px" %)
21 -|=(% style="width: 45px;" %)#|=(% style="width: 241px;" %)Option
22 -|(% style="width:45px" %) a|(% style="width:241px" %) OAuth 2.0 - Authorization Code
23 -|(% style="width:45px" %) b|(% style="width:241px" %) REST - Basic Auth
24 -|(% style="width:45px" %) c|(% style="width:241px" %) REST - Client Certificate
25 -|(% style="width:45px" %) d|(% style="width:241px" %) REST - Header Mapper
26 -|(% style="width:45px" %) e|(% style="width:241px" %) OAuth 2.0 - Client Credentials
27 -|(% style="width:45px" %) f|(% style="width:241px" %) REST - SSL
28 -|(% style="width:45px" %) g|(% style="width:241px" %) Dynamic Token
29 -|(% style="width:45px" %) h|(% style="width:241px" %) Token
30 -|(% style="width:45px" %) i|(% style="width:241px" %) No Authentication (Fire & Forget)
31 -)))
22 +None
23 +
24 +//Would you please consult the privacy policy of eMagiz at the following [[link>>https://www.emagiz.com/privacy-policy/||target="blank"]])))
25 +
26 +((()))
32 32  {{/container}}
33 33  {{/container}}