Authorization - Calling a SOAP Webservice

{{container}}{{container layoutStyle="columns"}}(((

When talking to external parties via a SOAP web service they will most likely require some form of authorization. Within eMagiz, you have various options to send the correct authorization towards that external system. The one that is most used when communicating with external parties is a username/password combination (i.e. basic authentication). In this microlearning, we will focus on that scenario and discuss some of the other possibilities that eMagiz offers out of the box.

3

4

Should you have any questions, please contact academy@emagiz.com.

5

6

== 1. Prerequisites ==

7

* Basic knowledge of the eMagiz platform

8

9

== 2. Key concepts ==

10

This microlearning centers around the endpoint check.

11

12

By authorization, we mean: The act of proving to the external party that you are indeed who you claim to be

13

14

* Main form used is a username/password combination (i.e. basic authentication)

15

* Other standard eMagiz options are:

16

** Mendix authentication

17

** Metacom authentication

18

** Zimbra authentication

19

20

== 3. Authorization - Calling a SOAP Webservice ==

21

22

When talking to external parties via a SOAP web service they will most likely require some form of authorization. Within eMagiz, you have various options to send the correct authorization towards that external system. The one that is most used when communicating with external parties is a username/password combination (i.e. basic authentication). In this microlearning, we will focus on that scenario and discuss some of the other possibilities that eMagiz offers out of the box.

23

24

* Main form used is a username/password combination (i.e. basic authentication)

25

* Other standard eMagiz options are:

26

** Mendix authentication

27

** Metacom authentication

28

** Zimbra authentication

29

30

=== 3.1 Username password credentials ===

31

32

To set up the authorization we need to navigate to the Create phase of eMagiz and open the flow in which we want to add the authorization. Here we can add a support object called HTTP Components message sender.

33

34

[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-authorization-calling-a-soap-webservice--http-components-message-sender.png]]

35

36

When you open the component you can choose Username password credentials in the drop-down and fill in properties to represent the password and username.

37

38

[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-authorization-calling-a-soap-webservice--http-components-message-sender-filled-in.png]]

39

40

After you have done so you can link the support object to the functional component by double-clicking on the functional component, navigate to the Advanced tab and select the correct message sender.

41

42

[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-authorization-calling-a-soap-webservice--link-message-sender.png]]

43

44

=== 3.2 Alternatives ===

45

46

Some alternatives that eMagiz offers for authentication in combination with calling a SOAP web service are:

47

48

* Mendix authentication

49

* Metacom authentication

50

* Zimbra authentication

51

52

To learn the specifics of each of these options please read the help text on these components to determine whether they can help you build a successful integration.

53

54

== 4. Key takeaways ==

55

56

* Main form used is a username/password combination (i.e. basic authentication)

57

* Other standard eMagiz options are:

58

** Mendix authentication

59

** Metacom authentication