Changes for page ClientID OAuth - Check

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-SOAP Web service Connectivity
	1	+ClientID OAuth - Check

Content

...	...	@@ -2,40 +2,27 @@
2	2	{{container layoutStyle="columns"}}
3	3	(((
4	4	== About ==
5		-This store element will allow you to create an easy connection to SOAP based web services. XML data can be send to these web services, and for each connectivity type there is a Flow Fragment available.
	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.
6	6
7	7	== Documentation ==
8	8
9	9	==== 1. How to use====
10		-Ensure to locate the right connectivity method and import the right flow fragment.
	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.
11	11
12	12	==== 2. Keynotes & restrictions====
13	13
14		-* These flow fragments will contain only the eMagiz components to make a call to a SOAP based webservice.
15		-* The basic authentication flow fragment requires empty key and trust store that are to be added separately. These are not included in this store component.
	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	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		-[[https:~~/~~/emagiz.github.io/docs/microlearning/novice-soap-webservice-connectivity-authorization-calling-a-soap-webservice>>url:https://emagiz.github.io/docs/microlearning/novice-soap-webservice-connectivity-authorization-calling-a-soap-webservice]]
22	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/?>>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		-((((% border="2" cellpadding="10" cellspacing="10" style="width:292px" %)
29		-|=(% style="width: 45px;" %)#|=(% style="width: 241px;" %)Option
30		-|(% style="width:45px" %) a|(% style="width:241px" %) Basic Authentication
31		-|(% style="width:45px" %) b|(% style="width:241px" %) WS Addressing - Call back
32		-|(% style="width:45px" %) c|(% style="width:241px" %) Client certificate
33		-|(% style="width:45px" %) d|(% style="width:241px" %) Mapped headers
34		-|(% style="width:45px" %) e|(% style="width:241px" %) Token based - static
35		-|(% style="width:45px" %) f|(% style="width:241px" %) Token based - dynamic
36		-|(% style="width:45px" %) g|(% style="width:241px" %) SSL
37		-|(% style="width:45px" %) h|(% style="width:241px" %) No authentication
38		-|(% style="width:45px" %) i|(% style="width:241px" %) Dynamic URL
39		-)))
	26	+((()))
40	40	{{/container}}
41	41	{{/container}}