Changes for page ClientID OAuth - Check

Last modified by Erik Bakker on 2024/06/03 12:37

From version 3.1
edited by Erik Bakker
on 2022/04/29 15:21
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,34 +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 +== Documentation ==
7 7  
8 -a. Note that you need to select the valid authentication based on the requirement of the external system.
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.
9 9  
10 -**3. License Information**
11 -Part of the standard license agreement as agreed upon when using the store for the first time.
12 +==== 2. Keynotes & restrictions====
12 12  
13 -**4. Relevant eMagiz Academy Microlearnings**
14 -[[https:~~/~~/emagiz.github.io/docs/microlearning/intermediate-rest-webservice-connectivity-index>>url:https://emagiz.github.io/docs/microlearning/intermediate-rest-webservice-connectivity-index]]
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).
15 15  
17 +==== 3. License Information====
18 +Part of the standard license agreement as agreed upon when using the store for the first time.
16 16  
17 -Would you please consult the privacy policy of eMagiz at the following link: [[https:~~/~~/www.emagiz.com/privacy-policy/?>>url:https://www.emagiz.com/privacy-policy/?]])))
20 +==== 4. Relevant eMagiz Academy Microlearnings====
18 18  
22 +None
19 19  
24 +//Would you please consult the privacy policy of eMagiz at the following [[link>>https://www.emagiz.com/privacy-policy/||target="blank"]])))
20 20  
21 -((((% border="2" cellpadding="10" cellspacing="10" style="width:292px" %)
22 -|=(% style="width: 45px;" %)#|=(% style="width: 241px;" %)Option
23 -|(% style="width:45px" %) a|(% style="width:241px" %) OAuth 2.0 - Authorization Code
24 -|(% style="width:45px" %) b|(% style="width:241px" %) REST - Basic Auth
25 -|(% style="width:45px" %) c|(% style="width:241px" %) REST - Client Certificate
26 -|(% style="width:45px" %) d|(% style="width:241px" %) REST - Header Mapper
27 -|(% style="width:45px" %) e|(% style="width:241px" %) OAuth 2.0 - Client Credentials
28 -|(% style="width:45px" %) f|(% style="width:241px" %) REST - SSL
29 -|(% style="width:45px" %) g|(% style="width:241px" %) Dynamic Token
30 -|(% style="width:45px" %) h|(% style="width:241px" %) Token
31 -|(% style="width:45px" %) i|(% style="width:241px" %) No Authentication (Fire & Forget)
32 -)))
26 +((()))
33 33  {{/container}}
34 34  {{/container}}