custom-permissions-mapping.properties and Studio 7.3.3

1
0
-1

Hello

I am using BonitaBPM Studio 7.3.3 community edition on OSX and I want to deploy a REST API extension to test my UIDesigner forms that use this API.

Previously - on windows / Studio 7.0.x - I could modify the custom-permissions-mapping.properties to add a profile|User=[myApiPermissions] and this would do the trick but I cannot find where this file is on OS.X

I tryed to change those files:

./plugins/org.bonitasoft.studio.console.libs_7.3.3.201610061535/tomcat/setup/platform_conf/initial/tenant_template_portal/custom-permissions-mapping.properties

./workspace/tomcat/setup/platform_conf/initial/tenant_template_portal/custom-permissions-mapping.properties

Any hint where this file should be?

Comments

Submitted by g.lapierre on Tue, 01/03/2017 - 16:27

looks like this is related to 7.3.x bonita_home removal. This parameter is stored into an h2 database. I tryed to use setup.sh but I am not sure which one I am supposed to use (the one in org.bonitasoft.studio.console.libs_7.3.3.201610061535 states that platform is not created. Run 'setup init' first)

1 answer

1
0
-1
This one is the BEST answer!

Hi,

When you server is up and running you can pull the configuration from the DB to your local files by using the command 'setup.sh pull'. To configure the access to the database, modify the file database.properties.

Once pulled, the configuration files should be located in the folder 'current'. There you'll find all the configuration files related to the engine. In the folder current/tenants/1/tenant_portal/, you have the file custom-permission-mapping.properties.

Once modified, you can push the configuration back by using the command setup.sh push. Restart the engine to apply the new configuration.

Cheers

Comments

Submitted by g.lapierre on Wed, 01/04/2017 - 11:39

Does that work for the Studio?

Submitted by Lionel Palacin on Wed, 01/04/2017 - 11:45

Yes.

The setup command is located in workspace/tomcat/setup

The default configuration to access the H2 Db doesn't work tho. You have to modify the file database.properties to point to jdbc:h2:tcp://localhost:9091/bonita_journal.db;MVCC=TRUE;DB_CLOSE_ON_EXIT=FLASE;IGNORECASE=TRUE;

Submitted by g.lapierre on Wed, 01/04/2017 - 14:15

Thanks, with the modified URL it works. The first pull seems to indicate I somehow had managed to change the configuration but I still had 403 forbidden errors while now they disappeared!

Notifications