[dna-issues] [JBoss JIRA] Updated: (DNA-596) Relax security by default to be more accessible to new users

[Brian Carothers (JIRA)]

     [ https://jira.jboss.org/jira/browse/DNA-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-596:
--------------------------------

    Attachment: DNA-596.patch


Per discussion with Jason and Randall, the attached patch makes the following changes:

1.  Makes the default anonymous (guest) user access "admin"
2.  Makes the FileSystem error message for attempts to update a source that does not allow updates more specific:
        The source "{0}" does not allow updates.  Set the "updatesAllowed" property to "true" on the repository source (connector) to enable updates. 
3.  Modifies the Getting Started Guide to highlight the default settings and provide examples for how to modify the setting through XML or programmatic or XML configuration.
4.  Modifies the Reference Guide to describe the impact of the ANONYMOUS_USER_ROLES setting and provide a reference to the examples in the Getting Started Guide

> Relax security by default to be more accessible to new users
> ------------------------------------------------------------
>
>                 Key: DNA-596
>                 URL: https://jira.jboss.org/jira/browse/DNA-596
>             Project: DNA
>          Issue Type: Feature Request
>          Components: Documentation, Examples
>    Affects Versions: 0.6
>            Reporter: Jason Dobies
>            Assignee: Brian Carothers
>             Fix For: 0.7
>
>         Attachments: DNA-596.patch
>
>
> While doing a quick prototype/proof of concept using DNA for the first time, I ran into two issues:
> - I wasn't able to simply login using Repository.login(). I had to configure and use JAAS.
> - I wasn't able to write files to a FileSystemSource, getting an error similar to "source does not support update"
> The latter was fixed by adding the configuration property "updatesAllowed" and setting it to true.
> After some discussion in the chat room with bcar and rhauch, it sounds like everyone is on board making the initial user experience easier (avoiding the above two issues). A potential side JIRA to this would be to add documentation on hardening DNA for a production deployment, which would mention things such as disabling anonymous login and file writing (assuming that's desired).
> On a personal note: the docs do a really good job of laying out the other steps I needed to take with regard to creating the configuration, engine, repository, and session. Once I got JAAS configured the code I had written to interact with DNA worked fine.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira