Changes for page Regex Match - SpEL
Last modified by Erik Bakker on 2023/01/31 10:28
From version 3.1
edited by Erik Bakker
on 2022/04/29 15:21
on 2022/04/29 15:21
Change comment:
There is no comment for this version
To version 15.1
edited by Erik Bakker
on 2022/05/02 10:24
on 2022/05/02 10:24
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 - REST - Request& Response1 +Auth Check - SpEL - Content
-
... ... @@ -1,34 +1,31 @@ 1 1 {{container}} 2 2 {{container layoutStyle="columns"}} 3 -(((**~1. How to use** 4 -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. 3 +((( 4 +== About == 5 +With the help of this SpEL expression, you can easily determine whether someone is authenticated or not when calling your web service. Based on the result of the statement you could decide whether a message may continue or not. 5 5 6 - **2.Keynotes & restrictions**7 +== Documentation == 7 7 8 -a. Note that you need to select the valid authentication based on the requirement of the external system. 9 +==== 1. How to use==== 10 +With the help of this SpEL expression, you can easily determine whether someone is authenticated or not when calling your web service. Based on the result of the statement you could decide whether a message may continue or not. 9 9 10 -**3. License Information** 12 +==== 2. Keynotes & restrictions==== 13 + 14 +* Note that this is an example of how you can use the SpEL expression within eMagiz. 15 +* The key element of this SpEL expression is that it allows you to verify whether an external party is allowed to call your web service. 16 +* Note that you need to rename the headers and the header references within the expression to reflect the system for which you have defined the web service. 17 + 18 +==== 3. License Information==== 11 11 Part of the standard license agreement as agreed upon when using the store for the first time. 12 12 13 -**4. Relevant eMagiz Academy Microlearnings** 14 -[[https:~~/~~/emagiz.github.io/docs/microlearning/intermediate-rest-webservice-connectivity-index>>url:https://emagiz.github.io/docs/microlearning/intermediate-rest-webservice-connectivity-index]] 21 +==== 4. Relevant eMagiz Academy Microlearnings==== 15 15 23 +[[https:~~/~~/emagiz.github.io/docs/microlearning/advanced-data-handling-spel-expressions>>url:https://emagiz.github.io/docs/microlearning/advanced-data-handling-spel-expressions]] 16 16 17 -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 +//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/?]]))) 18 18 19 19 20 20 21 -((((% border="2" cellpadding="10" cellspacing="10" style="width:292px" %) 22 -|=(% style="width: 45px;" %)#|=(% style="width: 241px;" %)Option 23 -|(% style="width:45px" %) a|(% style="width:241px" %) OAuth 2.0 - Authorization Code 24 -|(% style="width:45px" %) b|(% style="width:241px" %) REST - Basic Auth 25 -|(% style="width:45px" %) c|(% style="width:241px" %) REST - Client Certificate 26 -|(% style="width:45px" %) d|(% style="width:241px" %) REST - Header Mapper 27 -|(% style="width:45px" %) e|(% style="width:241px" %) OAuth 2.0 - Client Credentials 28 -|(% style="width:45px" %) f|(% style="width:241px" %) REST - SSL 29 -|(% style="width:45px" %) g|(% style="width:241px" %) Dynamic Token 30 -|(% style="width:45px" %) h|(% style="width:241px" %) Token 31 -|(% style="width:45px" %) i|(% style="width:241px" %) No Authentication (Fire & Forget) 32 -))) 29 +((())) 33 33 {{/container}} 34 34 {{/container}}