Im also experiencing this. Also runs docker bonita image. Setting the profile to user will not run the process and will give a 403 error. But when you switch to admin, everything is working out fine.
To solve this, a security file must be configured using the setup tool.
1º Go into the container through a terminal
docker exec -it container_name bash
2º Once inside go to /opt/bonita/BonitaCommunity-7.11.2/setup (adapt to your version number)
3º Execute ./setup.sh pull, this creates or updates the folder /opt/bonita/BonitaCommunity-7.11.2/setup/platform_conf/current that contains all the configuration.
4º Edit the following file /opt/bonita/BonitaCommunity-7.11.2/setup/platform_conf/current/tenants/1/tenant_portal/security-config.properties and set the property security.rest.api.authorizations.check.enabled false ( defaults is true)
5º Go back to the /opt/bonita/BonitaCommunity-7.11.2/setup folder and execute ./setup.sh push to upload the changes
6º Restart the container in order to commit the changes.
Have you tried to test it in your local environment?
I will reproduce it on my side but I assume it might not be related to your Docker environment but rather to your profiles definition vs actor mapping.
In order to understand what's going on, we will need more information; can both of you tell me which REST API you are using, what steps you have performed to deploy with Docker? Are you both using Community Edition Docker image? Have you logs to share?
Bonitasoft empowers development teams with Bonita, the open-source and extensible platform to solve the most demanding process automation use cases. The Bonita platform accelerates delivery of complex applications with clear separation between capabilities for visual programming and for coding. Bonita integrates with existing solutions, orchestrates heterogeneous systems, and provides deep visibility into processes across the organization.