[ 
https://issues.apache.org/jira/browse/MARMOTTA-641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15320151#comment-15320151
 ] 

Sergio Fernández edited comment on MARMOTTA-641 at 6/8/16 7:05 AM:
-------------------------------------------------------------------

[[email protected]], you're right, Marmotta comes with three profiles by 
default, as described at 
http://marmotta.apache.org/platform/security-module.html

The configuration is based on ACL rules. Those rules are written to the main 
configuration file ({{system-config.properties}}), so you can easily customize 
them; for instance it's [recommended for the admin-ui for production 
systems|http://marmotta.apache.org/configuration.html#production]. You can find 
more details at http://marmotta.apache.org/platform/security-module.html#Rules

You can find the implementation of the default profiles at 
https://github.com/apache/marmotta/tree/develop/platform/marmotta-security/src/main/resources
 So you can play to combine them as you need. Of course ask at dev@marmotta for 
help. So, when you have implemented the profile you consider useful for the 
project, you can send a pull request to the project with the new one.


was (Author: wikier):
[[email protected]], you're right, Marmotta comes with three profiles by 
default, as described at 
http://marmotta.apache.org/platform/security-module.html

The configuration is based on ACL rules such as: Those rules are written to the 
main configuration file ({{system-config.properties}}), so you can easily 
customize them; for instance it's [recommended for the admin-ui for production 
systems|http://marmotta.apache.org/configuration.html#production]. You can find 
more details at http://marmotta.apache.org/platform/security-module.html#Rules

You can find the implementation of the default profiles at 
https://github.com/apache/marmotta/tree/develop/platform/marmotta-security/src/main/resources
 So you can play to combine them as you need. Of course ask at dev@marmotta for 
help. So, when you have implemented the profile you consider useful for the 
project, you can send a pull request to the project with the new one.

> More flexible default security profiles
> ---------------------------------------
>
>                 Key: MARMOTTA-641
>                 URL: https://issues.apache.org/jira/browse/MARMOTTA-641
>             Project: Marmotta
>          Issue Type: Improvement
>          Components: Admin Interface, Web Services
>    Affects Versions: 3.3.0
>         Environment: Application accessing the LDP interface
>            Reporter: Rob Atkinson
>
> The LDP interface is designed so another application can manage the content. 
> The Web admin is useful during development, deployment setup, testing and 
> monitoring,  however all real work will be done by service integration.
> There are thus two key deployment patterns that are not well supported by the 
> default profiles (simple, standard)
> 1) an application on the local machine with an integrated marmotta install, 
> accessing it via web services
> 2) a "database service" in the cloud - where access is from multiple 
> applications.
> In each case, it should be possible to access the web admin without denying 
> LDP service access.  These are currently mutually exclusive with "simple" and 
> "standard" - making it neither simple or standard behaviour :-)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to