[
https://issues.apache.org/jira/browse/DERBY-5522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13230464#comment-13230464
]
Rick Hillegas commented on DERBY-5522:
--------------------------------------
Hi Kim,
I can reproduce the problem you are seeing. The actual connection url you are
passing to DriverManager is
jdbc:derby:nativeAuthDB
I think that you want the connection url to look like this:
jdbc:derby:nativeAuthDB;user=sysadm;password=i2have3power;create=true
The trailing attributes on that connection url appear in your printout, but
they are just appended by your println() call. They don't actually appear in
the connection url passed to DriverManager.
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: CreateNativeUsers.java, NativeAuthExampleClient1.java,
> NativeAuthExampleClient2.java, NativeAuthExampleEmbedded.java,
> NativeAuthExampleEmbedded.java, NativeAuthExampleEmbedded.java,
> NativeAuthExampleEmbedded.java, NativeAuthExampleEmbedded.java,
> NativeAuthExampleEmbedded.java, UseNativeUsers.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
