[
https://issues.apache.org/jira/browse/DERBY-5522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13226482#comment-13226482
]
Kim Haase commented on DERBY-5522:
----------------------------------
Great, so all those access properties can be scrapped along with the rest of
the builtin stuff. I will use roles and grant statements only then. I guess we
should not have left the old properties in the SQL authorization examples.
Should they also be listed as deprecated and not to be documented in the future?
So would you normally set up roles in the credentials db, or only in the
clients that used it? I suppose you might want to grant different access to
different users for different applications, so doing it in the clients would
give you greater flexibility?
> 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
