db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5522) Document the NATIVE authentication scheme.
Date Tue, 20 Mar 2012 17:25:38 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13233582#comment-13233582
] 

Kim Haase commented on DERBY-5522:
----------------------------------

The NativeAuthExampleEmbedded application used to behave differently from your description
-- but with the latest changes, it no longer works that way. The error messages are not crystal
clear, though. When I tried to run the version attached above, this was the error:

Trying to connect to jdbc:derby:nativeAuthEmbDB;user=sysadm;create=true
Connected to database jdbc:derby:nativeAuthEmbDB;user=sysadm;create=true
Storing some sample users in the database.

---SQLException Caught---

SQLState:   4251K
Severity: 30000
Message:  The first credentials created must be those of the DBO.

So I switched the order of user creation and got

Trying to connect to jdbc:derby:nativeAuthEmbDB;user=sysadm;create=true
Connected to database jdbc:derby:nativeAuthEmbDB;user=sysadm;create=true
Storing some sample users in the database.
Turning on NATIVE authentication.

---SQLException Caught---

SQLState:   XCY05
Severity: 30000
Message:  Invalid change of the derby.authentication.provider property. Once set to NATIVE
authentication, this property cannot be changed.

The problem is that I'm using SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY to set the provider to
NATIVE, which is now illegal. The provider was never set before, to NATIVE or anything else.
So the message is misleading.

                
> 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, CreateNativeUsers.java, DERBY-5522-devguide.diff,
DERBY-5522-devguide.stat, DERBY-5522-devguide.zip, NativeAuthExampleClient1.java, NativeAuthExampleClient2.java,
NativeAuthExampleEmbedded.java, NativeAuthExampleEmbedded.java, NativeAuthExampleEmbedded.java,
NativeAuthExampleEmbedded.java, NativeAuthExampleEmbedded.java, NativeAuthExampleEmbedded.java,
UseNativeUsers.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

        

Mime
View raw message