Camunda Run is the most recent addition to the list of Camunda Platform distributions. It combines extensive configurability with simplicity while making Camunda Platform more accessible to non-Java developers. In this talk I will demonstrate how to solve some of the most common problems we see users face like securing your REST API, enabling CORS and more. We will have a closer look at new Run features involving OpenAPI and explore different ways to configure Camunda Run to make it ready for production.

1. Tips on how to build Camunda Run for
production
Miklas Boskamp, Software Developer @ Camunda

2. 2
The Basics
● What?
○ Lightweight distribution of Camunda Platform
● Why?
○ simple to configure and use
○ handles advanced use-cases
● Who?
○ developing against Camunda Platform?
○ are non-Java developer?
○ looking for a fast user-experience?
○ run Camunda Platform in production?
○ all of the above?
Get Started With
Camunda Run

3. 3
What will we do today?
● Presets for production environments
● REST API security
● Swagger UI in Camunda Run
● Cross-Origin Resource Sharing (CORS)
● Custom script engines

4. 4
The production.yml file
• location: /configuration/production.yml
• based on Security Instructions guide
• supports Camunda Run and Spring Boot Starter properties
• enabled with --production argument

5. 5
production.yml
Secure the REST API
Camunda Run:
1. enable configuration flag
camunda.bpm:
run:
auth.enabled: true
Tomcat:
1. locate web.xml file
2. register servlet filter
3. register authentication provider
4. configure filter mapping
docs
docs

6. 6
Swagger UI included in Run
• enabled by default in non-production
• enabled in production via CLI argument
C:camunda-bpm-run>start.bat --webapps --rest --swaggerui
WebApps enabled
REST API enabled
Swagger UI enabled
____ _ ____ _ _ __ ____
/ ___| __ _ _ __ ___ _ _ _ __ __| | __ _ | _ | | __ _| |_ / _| ___ _ __ _ __ ___ | _ _ _ _ __
| | / _` | '_ ` _ | | | | '_ / _` |/ _` | | |_) | |/ _` | __| |_ / _ | '__| '_ ` _ | |_) | | | | '_
| |__| (_| | | | | | | |_| | | | | (_| | (_| | | __/| | (_| | |_| _| (_) | | | | | | | | | _ <| |_| | | | |
____/__,_|_| |_| |_|__,_|_| |_|__,_|__,_| |_| |_|__,_|__|_| ___/|_| |_| |_| |_| |_| ___,_|_| |_|
Spring-Boot: (v2.4.3)
Camunda Platform: (v7.15.0-ee)

7. 7
production.yml
Configure Cross-Origin Resource Sharing
Camunda Run:
1. enable configuration flag
camunda.bpm:
run:
enabled: true
allowed-origins: "*"
WildFly:
1. locate standalone.xml file
2. add new subsystem
3. register filters
4. register handlers
forum post
docs
Spring Boot:
1. create configuration
properties
2. create FilterRegistrationBean
3. add CORS filter
4. double check filter order

8. 8
Enable Custom Script Engines
Camunda Run:
1. copy JAR into userlib directory
camunda-bpm-run
└── configuration/
└── userlib/
└── jython.jar
WildFly:
1. create new module
2. copy JAR into module
3. create module.xml
docs

9. 9
Why Run?
• works out of the box
• comes pre-configured for production
• lightweight (~50MB)
• powerful configuration options
• Camunda Spring Boot Starter configuration
• simplifies common configuration problems

10. 10
CORS
Swagger UI
Custom Script Engines
Password Policies
HTTPS
DB Connection
Logging
REST API Authentication
Deserialization Type Validation
LDAP
History Level
Resource Auto-Deployment
Job Executor
REST-Only Mode
Webapp-Only Mode
CSRF Prevention
Webapp Header Security
Initial Admin User
History Cleanup
Resource Whitelisting

11. Questions?