mirror of
https://github.com/clearlinux/docs.git
synced 2026-09-02 20:01:51 +00:00
update documentation links to 7.0.0 version
This commit is contained in:
+4
-4
@@ -12,7 +12,7 @@ Bonita BPM is an open-source business process management and workflow suite crea
|
||||
|
||||
docker run --name bonita -d -p 8080:8080 bonita
|
||||
|
||||
This will start a container running the [Tomcat Bundle](http://documentation.bonitasoft.com/tomcat-bundle-1) with Bonita BPM Engine + Portal. As you didn't specify any environment variables it's almost like if you have launched the Bundle on your host using startup.{sh|bat} (with security hardening on REST and HTTP APIs, cf Security part). It means that Bonita BPM uses a H2 database here.
|
||||
This will start a container running the [Tomcat Bundle](http://documentation.bonitasoft.com/tomcat-bundle-2) with Bonita BPM Engine + Portal. As you didn't specify any environment variables it's almost like if you have launched the Bundle on your host using startup.{sh|bat} (with security hardening on REST and HTTP APIs, cf Security part). It means that Bonita BPM uses a H2 database here.
|
||||
|
||||
You can access to the portal on http://localhost:8080/bonita and login using the default credentials : install / install
|
||||
|
||||
@@ -65,11 +65,11 @@ This docker image ensures to activate by default both static and dynamic authori
|
||||
|
||||
- REST API authorization
|
||||
|
||||
- [Static authorization checking](http://documentation.bonitasoft.com/rest-api-authorization#static)
|
||||
- [Static authorization checking](http://documentation.bonitasoft.com/rest-api-authorization-0#static)
|
||||
|
||||
- [Dynamic authorization checking](http://documentation.bonitasoft.com/rest-api-authorization#dynamic)
|
||||
- [Dynamic authorization checking](http://documentation.bonitasoft.com/rest-api-authorization-0#dynamic)
|
||||
|
||||
- [HTTP API](http://documentation.bonitasoft.com/rest-api-authorization#activate)
|
||||
- [HTTP API](http://documentation.bonitasoft.com/rest-api-authorization-0#activate)
|
||||
|
||||
But for specific needs you can override this behavior by setting HTTP_API to true and REST_API_DYN_AUTH_CHECKS to false :
|
||||
|
||||
|
||||
Reference in New Issue
Block a user