Skip to Content

Changes for page ClientID OAuth - Check

Last modified by Erik Bakker on 2024/06/03 12:37
From version 20.1
edited by Erik Bakker
on 2024/06/03 12:09
Change comment: There is no comment for this version
To version 17.1
edited by Erik Bakker
on 2022/05/02 10:01
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -ClientID OAuth - Check
1 +Basic Auth - Check
Content
... ... @@ -2,17 +2,18 @@
2 2  {{container layoutStyle="columns"}}
3 3  (((
4 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 +With the help of this store component, you can validate if the basic authentication provided by one single entity is conformed to what you would have expected. In case that is not true, eMagiz will return 'Unauthorized' to the client.
6 6  
7 7  == Documentation ==
8 8  
9 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.
10 +With the help of this store component, you can validate if the basic authentication provided by one single entity is conformed to what you would have expected. In case that is not true, eMagiz will return 'Unauthorized' to the client.
11 11  
12 12  ==== 2. Keynotes & restrictions====
13 13  
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).
14 +* Note that this functionality can only validate one specific set of credentials. If multiple clients call your endpoint you should change the groovy script accordingly.
15 +* Any custom additions that are needed for your specific use cases need to be created by you and eMagiz will not create it for you.
16 +* Please check out the following link to learn a bit more about Groovy: https://www.tutorialspoint.com/groovy/index.htm
16 16  
17 17  ==== 3. License Information====
18 18  Part of the standard license agreement as agreed upon when using the store for the first time.
... ... @@ -21,8 +21,10 @@
21 21  
22 22  None
23 23  
24 -//Would you please consult the privacy policy of eMagiz at the following [[link>>https://www.emagiz.com/privacy-policy/||target="blank"]])))
25 +//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/?]])))
25 25  
27 +
28 +
26 26  ((()))
27 27  {{/container}}
28 28  {{/container}}