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
on 2024/06/03 12:09
Change comment:
There is no comment for this version
To version 4.1
edited by Erik Bakker
on 2022/05/02 08:17
on 2022/05/02 08:17
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 - ClientIDOAuth-Check1 +SOAP Web service Connectivity - Content
-
... ... @@ -1,28 +1,40 @@ 1 1 {{container}} 2 2 {{container layoutStyle="columns"}} 3 3 ((( 4 -= =About ==5 - Withthe help of this storecomponent,youcan validateiftheclientID providedby onesingleentity conformedtowhatyouwouldhave expected.Incase that is nottrue,eMagizwillreturna403Forbiddenothe client.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. 6 6 7 -= =Documentation ==7 += Documentation = 8 8 9 - ====1. How to use====10 -With th e help of this store component, you canvalidateif theclientIDprovidedbyone singleentity conformedtowhatyouwould haveexpected.Incasethats nottrue, eMagizwill returna403 Forbidden totheclient.9 + **~1. How to use** 10 +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. 11 11 12 - ====2. Keynotes & restrictions====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 +a. Note that you need to select the valid authentication based on the requirement of the external system. 16 16 17 - ====3. License Information====16 +**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 -==== 4. Relevant eMagiz Academy Microlearnings==== 19 +**4. Relevant eMagiz Academy Microlearnings** 20 +[[https:~~/~~/emagiz.github.io/docs/microlearning/intermediate-rest-webservice-connectivity-index>>url:https://emagiz.github.io/docs/microlearning/intermediate-rest-webservice-connectivity-index]] 21 21 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"]])))23 +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 26 -((())) 25 + 26 + 27 +((((% border="2" cellpadding="10" cellspacing="10" style="width:292px" %) 28 +|=(% style="width: 45px;" %)#|=(% style="width: 241px;" %)Option 29 +|(% style="width:45px" %) a|(% style="width:241px" %) OAuth 2.0 - Authorization Code 30 +|(% style="width:45px" %) b|(% style="width:241px" %) REST - Basic Auth 31 +|(% style="width:45px" %) c|(% style="width:241px" %) REST - Client Certificate 32 +|(% style="width:45px" %) d|(% style="width:241px" %) REST - Header Mapper 33 +|(% style="width:45px" %) e|(% style="width:241px" %) OAuth 2.0 - Client Credentials 34 +|(% style="width:45px" %) f|(% style="width:241px" %) REST - SSL 35 +|(% style="width:45px" %) g|(% style="width:241px" %) Dynamic Token 36 +|(% style="width:45px" %) h|(% style="width:241px" %) Token 37 +|(% style="width:45px" %) i|(% style="width:241px" %) No Authentication (Fire & Forget) 38 +))) 27 27 {{/container}} 28 28 {{/container}}