[
https://issues.apache.org/jira/browse/DERBY-5522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13229439#comment-13229439
]
Rick Hillegas commented on DERBY-5522:
--------------------------------------
Hi Kim,
In general, authorization is not affected by the kind of authentication
mechanism which Derby uses. The same authorization options are available
regardless of whether you use LDAP, custom, or BUILTIN.
NATIVE authentication slightly complicates this situation because NATIVE
authentication automatically turns on SQL authorization (and makes it
impossible to turn off SQL authorization).
I believe you are talking about the properties which configure the old-style
authorization scheme which Derby used before SQL authorization was introduced.
Those properties can be used with LDAP, custom, BUILTIN, and NATIVE
authentication.
Hope this helps,
-Rick
> 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, NativeAuthExampleEmbedded.java,
> 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
