Changes for page ClientID OAuth - Check
Last modified by Erik Bakker on 2024/06/03 12:37
From version 11.1
edited by Erik Bakker
on 2022/05/02 09:39
on 2022/05/02 09:39
Change comment:
There is no comment for this version
To version 21.1
edited by Erik Bakker
on 2024/06/03 12:36
on 2024/06/03 12:36
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -I fthenelse-SpEL1 +ClientID OAuth - Check - Content
-
... ... @@ -2,29 +2,27 @@ 2 2 {{container layoutStyle="columns"}} 3 3 ((( 4 4 == About == 5 -With the help of this store item, you caneasily execute an ifthen else statementwith thehelpof aSpELexpression tofilter out messages.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. In case this is true, a header with the name "client" is added to the flow which can be used further downstream to determine what to do with the message. 6 6 7 7 == Documentation == 8 8 9 9 ==== 1. How to use==== 10 -With the help of this store item, you caneasily execute an ifthen else statementwith thehelpof aSpELexpression tofilter out messages.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. In case this is true, a header with the name "client" is added to the flow which can be used further downstream to determine what to do with the message. 11 11 12 12 ==== 2. Keynotes & restrictions==== 13 13 14 -* Note that this i s an example ofhowyou canuse theSpELexpressionwithin eMagiz.15 -* The c rucial partofthisSpELexpressionisthecomparison between the inputvalue(mainlyaheader)anda propertylist.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). 16 16 17 17 ==== 3. License Information==== 18 - To use this store itemyouneedto secureanadditionallicenseon the eMagiz platform.Ifyouareinterestedinsucha licensepleasecontactusatproductmanagement@emagiz.com.18 +Part of the standard license agreement as agreed upon when using the store for the first time. 19 19 20 20 ==== 4. Relevant eMagiz Academy Microlearnings==== 21 21 22 - [[https:~~/~~/emagiz.github.io/docs/microlearning/advanced-data-handling-spel-expressions>>url:https://emagiz.github.io/docs/microlearning/advanced-data-handling-spel-expressions]]22 +None 23 23 24 -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/?]])))24 +//Would you please consult the privacy policy of eMagiz at the following [[link>>https://www.emagiz.com/privacy-policy/||target="blank"]]))) 25 25 26 - 27 - 28 28 ((())) 29 29 {{/container}} 30 30 {{/container}}