[
https://issues.apache.org/jira/browse/DERBY-5522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13226449#comment-13226449
]
Rick Hillegas commented on DERBY-5522:
--------------------------------------
Hi Kim,
I would consider this to be edge-case behavior. I regard the connection access
mode as a poor-man's substitute for SQL authorization. I believe it was added
because Derby did not support SQL authorization at the time. I suppose it lets
you deploy an application which has a class of users who can't write any data
at all, not even in their own schemas. I imagine that kind of restriction is
unusual. Thanks.
> Document the NATIVE authentication scheme.
> ------------------------------------------
>
> Key: DERBY-5522
> URL: https://issues.apache.org/jira/browse/DERBY-5522
> Project: Derby
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 10.9.0.0
> Reporter: Rick Hillegas
> Assignee: Kim Haase
> Attachments: NativeAuthExampleEmbedded.java,
> NativeAuthExampleEmbedded.java
>
>
> We should document NATIVE authentication after we have implemented the
> changes described on DERBY-866. The documentation changes are described by
> the functional spec UserManagement.html attached to that issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
