Private and public BPMs

[Javi Er]

Hi

 It would be possible to have private and public BPMs Diagrams?

 I mean, can I distribute some *.bpmn2 files that can´t be exported, viewed or modified inside of another user´s instalation of wildfly-jbpm?

 

He will be able to export, view and modify his own designs, but not mine.

He will be able to deploy/execute his own designs as well as mine.

 

He is the owner of the wildfly jbpm instance, therefore he knows all the user and passwords.

 

It could be:

- having his designs and mine in different organizational units?

- having my designs in a ciphered archive, and with a ofuscated library that will be capable of reading the designs only for execution purposes? How can I do this?

Thanks

Javi.

[Maciej Swiderski]

you can restrict access to repositories on workbench UI and git server level (hosted by workbench) but if someone has access as admin to modify the access rights on workbench (s)he can still alter them.

so besides the regular restrictions on workbench side there is not other design time authorization.

for deploy time, I see it better to distribute the kjars as binaries rather than source. kjar can include deployment descriptor which will enforce role membership on runtime. Deployment descriptor  can define that only given roles can view or execute process (see docs for this)

Maciej

--
You received this message because you are subscribed to the Google Groups "jBPM Usage" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jbpm-usage+...@googlegroups.com.
To post to this group, send email to jbpm-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jbpm-usage/12994f9f-f1ed-4d34-a6af-ceb978584346%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.