Skip to Content
Last modified by Erik Bakker on 2024/09/03 09:17
From version 22.1
edited by Erik Bakker
on 2024/06/21 12:52
Change comment: There is no comment for this version
To version 8.1
edited by Erik Bakker
on 2022/06/23 16:14
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -SMB - Dynamically Manipulate Settings
1 +Error Handling concerning GDPR
Parent
... ... @@ -1,1 +1,1 @@
1 -Main.eMagiz Academy.Microlearnings.Advanced Level.File based connectivity.WebHome
1 +WebHome
Default language
... ... @@ -1,1 +1,0 @@
1 -en
Content
... ... @@ -1,10 +1,11 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 -In a previous [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.File based connectivity.intermediate-file-based-connectivity-smb-connectivity.WebHome||target="blank"]] on this subject we discussed how to configure the various variants of SMB connectivity. In there we already mentioned that more dynamic options, such as automatically creating a "multi-level" directory (i.e. /root/sub) are complex to configure and require a different approach.
3 -
4 -In this microlearning we will look into how we can manipulate all settings on the SMB Session Factory to create dynamic values that are injected into the component when a message is processed by the flow.
2 +In eMagiz, all errors are raised when a process fails, and you want to have some form of logging end up in the Manage phase of eMagiz. The Manage phase of eMagiz is primarily accessible to support employees, employees working on the project, and in some cases, even more, people have at least view rights. You can imagine that when many people have access to potentially sensitive data, you should consider countermeasures. This way, you can reduce the chances of sensitive data ending up in the wrong hands. Some of the potential countermeasures are available within the platform. Some of them are procedural in nature. In this microlearning, we will learn what you can do to keep your data safe within eMagiz.
5 5  
6 6  Should you have any questions, don't hesitate to get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
7 7  
6 +* Last update: November 15th, 2021
7 +* Required reading time: 5 minutes
8 +
8 8  == 1. Prerequisites ==
9 9  
10 10  * Advanced knowledge of the eMagiz platform
... ... @@ -11,51 +11,47 @@
11 11  
12 12  == 2. Key concepts ==
13 13  
14 -This microlearning centers around dynamically manipulating settings on the SMB Session Factory.
15 +This microlearning centers around error handling concerning GDPR
16 +With GDPR, we mean The law on General Data Protection Regulation.
15 15  
16 -* When you dynamically need to create a directory or have multiple hosts that hosts file shares this option is the correct approach.
18 +* The GDPR is a European privacy regulation. It ensures the careful processing of personal data by businesses and organizations.
19 +* eMagiz has various security measures in place to keep your data safe
20 +* You also have a responsibility as a user how you use the data of the customer
17 17  
18 -== 3. Dynamically manipulate SMB Session Settings ==
19 19  
20 -In a previous [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.File based connectivity.intermediate-file-based-connectivity-smb-connectivity.WebHome||target="blank"]] we learned that we need an SMB Session Factory to setup the initial connection to the SMB drive. In this component there are five main settings that are of relevance.
21 21  
22 -* Host
23 -* Port
24 -* Username
25 -* Password
26 -* Share and directory
24 +== 3. Error Handling regarding GDPR ==
27 27  
28 -In theory each of these settings can be overwritten everytime a message is consumed and processed by the flow. In practice we see two main use cases that are relevant to mention in this microlearning as we see them currently being applied in our community.
29 -
30 -=== 3.1 Dynamic Host ===
26 +In eMagiz, all errors are raised when a process fails, and you want to have some form of logging end up in the Manage phase of eMagiz. The Manage phase of eMagiz is primarily accessible to support employees, employees working on the project, and in some cases, even more, people have at least view rights. You can imagine that when many people have access to potentially sensitive data, you should consider countermeasures. This way, you can reduce the chances of sensitive data ending up in the wrong hands. Some of the potential countermeasures are available within the platform. Some of them are procedural in nature. In this microlearning, we will learn what you can do to keep your data safe within eMagiz.
31 31  
32 -In case you have a multitude of SMB directories (i.e. shares) that span across a multitude of different host servers you are in need for a solution that can dynamically manipulate pre-existing information on the SMB session factory. In other words, you need to be able to override the default host configuration in the component with one that is determined based on information in the headers or message.
28 +In eMagiz, we value the security of your data. A detailed overview of how your data is secured within the platform and when data is exchanged can be found in our [Security Guide](../howto/security-guide.md). One of the additional measures you could take on our data models is to indicate whether the information stored in those attributes is confidential. More information on how that works exactly can be found in this [microlearning](intermediate-defining-your-message-structures-data-model-attribute-confidentiality.md).
33 33  
34 -To do so we need to add an additional component to the flow that will override the host setting. This component is called the "Standard service activator".
30 +Building on that, we have a store component available in the store with which you can replace the values in these attributes (in case the original payload is XML) with \*\*\*. The error message is still shown for an RCA to be performed, but the sensitive data is not accessible to the user.
35 35  
36 -[[image:Main.Images.Microlearning.WebHome@advanced-file-connectivity-dynamically-manipulate-smb-settings--standard-service-activator.png]]
32 +[[image:Main.Images.Microlearning.WebHome@advanced-understanding-error-handling-in-emagiz--store-component-gdpr-error-handling.png]]
37 37  
38 -In here we need to define an expression that will set the host based on a supplied value. Important in this expression is that we correctly reference the complete name of the SMB Session Factory support object in the flow and that once the host is set the actual message is passed along. An example of such an expression is {{code}}@'smb.gtwydynm.exit.support.smb-session'.setHost(headers.server) ?: #root{{/code}}. This expression will set the host based on the value in the header called "server" and once done will pass the full message to the output channel.
34 +In terms of process, you should know which data is sensitive in terms of GDPR and **not** store that information in external tools such as Postman and SOAP UI. Furthermore, it would be best to consider how you want to shape the notifications to prevent sensitive information from being willingly distributed to the eMail boxes of recipients.
39 39  
40 -[[image:Main.Images.Microlearning.WebHome@advanced-file-connectivity-dynamically-manipulate-smb-settings--standard-service-activator-filled-in.png]]
41 41  
42 -=== 3.2 Dynamic Share and Directory ===
43 -In eMagiz, all errors are raised when a process fails, and you want to have some form of logging end up in the Manage phase of eMagiz. The Manage phase of eMagiz is primarily accessible to support employees, employees working on the project, and in some cases, even more, people have at least view rights. You can imagine that when many people have access to potentially sensitive data, you should consider countermeasures. This way, you can reduce the chances of sensitive data ending up in the wrong hands. Some of the potential countermeasures are available within the platform. Some of them are procedural in nature. In this microlearning, we will learn what you can do to keep your data safe within eMagiz.
44 44  
45 -In eMagiz, we value the security of your data. A detailed overview of how your data is secured within the platform and when data is exchanged can be found in our [[Security Guide>>doc:Main.eMagiz Academy.Fundamentals.fundamental-emagiz-security-guide||target="blank"]]. One of the additional measures you could take on our data models is to indicate whether the information stored in those attributes is confidential. More information on how that works exactly can be found in this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Defining message structures.intermediate-defining-your-message-structures-data-model-attribute-confidentiality||target="blank"]].
38 +== 4. Assignment ==
46 46  
47 -Building on that, we have a [[store component>>doc:Main.eMagiz Store.Accelerators.Mask Values.WebHome||target="blank"]] available in the store with which you can replace the values in these attributes (in case the original payload is XML) with ~*~*~*. The error message is still shown for an RCA to be performed, but the sensitive data is not accessible to the user.
40 +Identify which attributes, if any, are sensitive in nature within your (Academy) project. This assignment can be completed within the (Academy) project you created/used in the previous assignment.
48 48  
49 -[[image:Main.Images.Microlearning.WebHome@advanced-understanding-error-handling-in-emagiz--store-component-gdpr-error-handling.png]]
42 +== 5. Key takeaways ==
50 50  
51 -In terms of process, you should know which data is sensitive in terms of GDPR and **not** store that information in external tools such as Postman and SOAP UI. Furthermore, it would be best to consider how you want to shape the notifications to prevent sensitive information from being willingly distributed to the eMail boxes of recipients.
52 -
53 -== 4. Key takeaways ==
54 -
55 55  * The GDPR is a European privacy regulation. It ensures the careful processing of personal data by businesses and organizations.
56 56  * eMagiz has various security measures in place to keep your data safe
57 57  * You also have a responsibility as a user how you use the data of the customer
58 58  
59 -== 5. Suggested Additional Readings ==
60 60  
61 -There are no suggested additional readings on this topic.)))((({{toc/}}))){{/container}}{{/container}}
49 +
50 +== 6. Suggested Additional Readings ==
51 +
52 +There are no suggested additional readings on this topic.
53 +
54 +== 7. Silent demonstration video ==
55 +
56 +As this is a more theoretical microlearning, we have no video for this.
57 +
58 +)))((({{toc/}}))){{/container}}{{/container}}
advanced-understanding-error-handling-in-emagiz--store-component-gdpr-error-handling.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ebakker
Size
... ... @@ -1,0 +1,1 @@
1 +3.9 KB
Content