Mule soft Meetup #3
Download as PPTX, PDF0 likes771 views
The document summarizes a Bangalore MuleSoft meetup event that took place on November 24th, 2018. It included a technical session on Mule 4 security features and GDPR compliance, as well as an open forum discussion. The meetup introduced MuleSoft organizers and partners and provided information on learning resources like MuleSoft U and instructor-led training courses.
![Mule 4 Security Features
Step 4 – Configure OAuth2
When you click on the “Authentication” tab in the HTTP Request
Configuration, some fields such as Authorization Url, Scopes, and
Token Url automatically filled out from the RAML. Make sure that
the below six fields are filled out in the OAuth2
configuration: Client Id, Client Secret, Redirection (Callback) URL,
Local Authorization Url, Access Token and Refresh Token.
Find Client Id, Client Secret and Redirection (Callback) URL from
GitHub. You can find this information in Settings -
> OAuth applications -> Developer applications in GitHub.
Pick a local authorization URL. Local authorization URL will be
used to initiate an“OAuth2.” and Write an MEL expression to
extract an access token and a refresh token. In GitHub’s case, it
doesn’t return a refresh token, so I will put the same expression
for the access token and refresh token.
(#[payload.’access_token’]) format of the response to this request
to the token URL is not defined in the OAuth spec, each service
could return a different response format.](https://image.slidesharecdn.com/meetup-190209140055/85/Mule-soft-Meetup-3-14-320.jpg)
Mule soft Meetup #3
- 1. Bangalore MuleSoft Meetup Group 24 Nov,2018: CloudHub Architecture and Integration deployment Patterns
- 2. 10:30 AM Introduction 10:45 AM Technical Session: Mule 4 Security Features, Mulesoft GDPR(General Data Protection Regulation) 12:30 PM Open forum discussion ( Q&A, Topics for next meetup, speakers for next meetup ) 01:00 PM Lunch break All contents © MuleSoft Inc.
- 4. Introductions About the organizer : – Gaurav – Senior Application Developer, Accenture – Rajesh – Senior Technology Architect , Infosys Partner: All contents © MuleSoft Inc. – Mahesh Shenoy – Director, Partner Enablement at MULESOFT.
- 5. All contents © MuleSoft Inc. Introductions 5 Introduce yourselves ! – Name – Background • What’s your experience with Anypoint platform? • Why are you here ? Expectations?
- 6. Mule 4 Security Features
- 7. Mule 4 Security Features Attack prevention Restrict access based on client IP addresses with drag and drop filters to guard your system from bad actors. Prevent replay attacks using easily configurable message expiry policies. Apply cyclic redundancy checks (CRC) to detect message tampering.
- 8. Mule 4 Security Features Secure Property Placeholder Secure properties can encrypt properties and store the encrypted text in secure properties files. We can configure a secure properties file with this module (<secure-properties:config>) The prefix secure:: is required for loading the key. <secure-properties:config name="Secure_Properties_Config" doc:name="Secure Properties Config" doc:id="3d35bc98-496c-4c54-b00e-38d072585ac7" file="config/application-name-${mule.env}.properties" key="${mule.key}" />
- 9. Mule 4 Security Features Encryption, digital signatures Maintain data integrity and confidentiality by encrypting all or part of confidential message payloads or storing access credentials in an encrypted vault. Preserve data integrity with digital signatures.
- 10. Mule 4 Security Features Download the security module's plug-in from the exchange in Anypoint Studio. encryption/decryption enhanced the secure key bases process, so now we need to generate a keystore file. “keytool.exe -genseckey -alias srccodes -keyalg AES -keystore aesKelltontech.jceks -keysize 128 -storeType JCEKS” Now, let's go to configure the "JCE encrypt" component to encrypt the data in flow with the below steps. Module configuration (global configuration): To use global configuration, we need to follow the below steps. JCE cryptography module
- 11. Mule 4 Security Features In the keystore file, "askKelltontech.jceks," which we have generated with the alias = 'srccodes' and password = '123456,' we can configure our app's global configuration. Refer to the global configuration in JCE encrypt component JCE cryptography module
- 12. Mule 4 Security Features Identity management Protect access to APIs and service endpoints by moving beyond usernames and passwords. Leverage proven security standards such as SAML, OAuth2, and WS-Security or use existing LDAP stores for authentication and authorization. Configure and apply API policies at runtime using Anypoint API Manager.
- 13. Mule 4 Security Features OAuth2 configuration in HTTP Connector Step 1 – Create a simple Mule flow in Studio Note: You can use the same HTTP Connector for both HTTP Listener and HTTP Request Step 2 – Configure the HTTP Listener When you click on HTTP Listener (the first HTTP) and click on + in the panel, you will see the HTTP Listener Configuration. For this demo, I will make my Mule app listen to localhost:8081/github. Step 3 – Get the GitHub RAML from Anypoint Exchange When you click on HTTP Request (the second HTTP in the flow), click on + in the panel, and you will see the HTTP Request Configuration. Click on “Search RAML in Exchange” to get the GitHub RAML from the Exchange.
- 14. Mule 4 Security Features Step 4 – Configure OAuth2 When you click on the “Authentication” tab in the HTTP Request Configuration, some fields such as Authorization Url, Scopes, and Token Url automatically filled out from the RAML. Make sure that the below six fields are filled out in the OAuth2 configuration: Client Id, Client Secret, Redirection (Callback) URL, Local Authorization Url, Access Token and Refresh Token. Find Client Id, Client Secret and Redirection (Callback) URL from GitHub. You can find this information in Settings - > OAuth applications -> Developer applications in GitHub. Pick a local authorization URL. Local authorization URL will be used to initiate an“OAuth2.” and Write an MEL expression to extract an access token and a refresh token. In GitHub’s case, it doesn’t return a refresh token, so I will put the same expression for the access token and refresh token. (#[payload.’access_token’]) format of the response to this request to the token URL is not defined in the OAuth spec, each service could return a different response format.
- 15. Mule 4 Security Features Step 5 – Select “emojis” in Path Since “emojis” doesn’t require any parameters, you can remove the following parameters in the header. Step 6 – Get a list of the emojis that GitHub supports After running the Mule app, initiate an “OAuth2 dance” by hitting the local authorization URL () specified in the HTTP Request Configuration. Once an access token is created, you can receive a list of the emojis GitHub supports by hitting .
- 16. GDPR
- 17. GDPR What is GDPR: All contents © MuleSoft Inc. GDPR is considered to be the most significant piece of European data protection legislation to be introduced in the EU in the last 20 years. This legislation has introduced a new information type called Personal Data which can be summarized as information. GDPR is not limited to EU-based businesses, it applies to global businesses that provide goods and services to EU citizens. These businesses are required to be compliant with GDPR, when the regulation takes effect.
- 18. GDPR How does Anypoint Platform handle Personal Data? All contents © MuleSoft Inc. MuleSoft’s Anypoint Platform is a fully customizable Platform as a Service (PaaS) which connects and manages data via cloud, hybrid, and on-premise offerings. Our platform is divided into two planes which separate the shared services and dedicated runtimes. 1. The Control Plane provides multi-tenant features and services, and manages the interconnected runtimes (i.e. CloudHub, Anypoint Exchange, and Runtime Manager). 2. The Runtime Plane can be a dedicated environment which performs the interconnection and pass through of data between connected systems.
- 19. Anypoint Exchange Anypoint DesignCenter Anypoint ManagementCenter MuleSoft Multi-Tenant VPC Customer Dedicated VPC Control plane Runtime plane Mule Runtime Engine AnypointConnectors Runtime Services GDPR All contents © MuleSoft Inc. Figure 1: Anypoint Platform
- 20. GDPR All contents © MuleSoft Inc. At the Control Plane level, MuleSoft has identified the following scenarios where Personal Data may be collected and used to provide you our products and services: Registering for Anypoint Platform Monitoring activity through logs Use of key features: Analytics, message queue, and object store At the Runtime Plane level, MuleSoft has identified the following scenarios where Personal Data may be handled as part of our products and services: Transmission of payload data Application logs of payload data
- 21. All contents © MuleSoft Inc. Quiz 15 Winners will receive a gift
- 22. Learn all about Mule 4 and more! Resources to learn
- 23. All contents © MuleSoft Inc. MuleSoft U 20 • Free! • Self-paced HTML-format courses with step-by-step instructions to go deep on any topic. • Available courses: - NEW - Development fundamentals (Mule 3 and 4) - NEW – Mule 4 for Mule 3 users - Flow Design - Getting started with Anypoint Platform (Mule 3 and 4) Register for MuleSoft U at https://training.mulesoft.com/category/mulesoftu
- 24. All contents © MuleSoft Inc. Instructor-led training 21 • 1 to 5 days, in person or online • 12 available courses • For all profiles: developers, architects, admins, IT ops, managers See all the learning paths available and register for a class at https://training.mulesoft.com Win 1 of 5 free instructor-led training courses by participating in our trivia later tonight!
- 25. All contents © MuleSoft Inc. More certifications to validate your skills 22 • Confirm mastery of concepts • Achieve industry recognition • Differentiate yourself in the marketplace – MCD – Level 1 (Mule 4) + Level 1 (Mule 4) DELTA – MCD – Integration and API Associate – MCD – API Design Associate – MCD – Integration Professional (Mule 3) – MuleSoft Certified Platform Architect – Level 1 – MuleSoft Certified Integration Architect – Level 1
- 26. QA & open discussion
- 27. All contents © MuleSoft Inc. Stay connected 24 Stay connected with Mule 4 Twitter: https:// twitter.com/Mulesoft Linkedin: https://www.linkedin.com/groups/6936034 / Facebook: https ://www.facebook.com/groups/Mulesoft/
- 28. Thank you ! See you next time Please send topic suggestions to the organizer