Changes for page ClientID OAuth - Check

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-ClientID OAuth - Check
	1	+Add Namespace

Content

...	...	@@ -2,27 +2,30 @@
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. If 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.
	5	+With the help of this transformation, you can easily add a namespace to your message. This is sometimes needed to communicate with an external system.
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. If 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.
	10	+With the help of this transformation, you can easily add a namespace to your message. This is sometimes needed to communicate with an external system.
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 is a custom XSLT that is designed for a specific cause.
	15	+* Always try to understand the context before you implement this transformation.
	16	+* Note that you need to define your specific namespace yourself when you want to implement this solution within your model.
16	16
17	17	==== 3. License Information====
18		-Part of the standard license agreement as agreed upon when using the store for the first time.
	19	+To use this store item you need to secure an additional license on the eMagiz platform. If you are interested in such a license please contact us at productmanagement@emagiz.com.
19	19
20	20	==== 4. Relevant eMagiz Academy Microlearnings====
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}}