db-derby-dev mailing list archives

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

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

Rick Hillegas commented on DERBY-5522:
--------------------------------------

Hi Kim,

>So it appears that setting the provider to NATIVE::LOCAL on an existing database by calling
syscs_util.syscs_set_database_property() does not work in ij, whereas it does work in a Java
program. Is that correct? 

Perhaps the simplest thing to say about this topic is that the behavior has changed as a result
of the spec change which I just checked in on DERBY-866: Now you can't set the authentication
provider to NATIVE::LOCAL by calling syscs_util.syscs_set_database_property() at all. Instead,
an existing database becomes a credentials DB (and that property is automatically set by Derby)
when the DBO calls syscs_create_user() to store her own credentials. This is true regardless
of whether you are trying to convert a database into a credentials db via ij or via some other
application.

But I think there is some other peculiarity which you are experiencing and which I don't understand.
When you create a database from scratch, the DBO's credentials are stored in SYS.SYSUSERS
(and the database is marked as a credentials DB) only if you have set the authentication provider
to NATIVE authentication via command line properties or derby.properties. This is supposed
to be true regardless of whether you are creating the database in an ij script or in some
other application. More specifically...

  derby.authentication.provider=NATIVE:credsDB:LOCAL

will cause every newly created database to be a credentials db. And

  derby.authentication.provider=NATIVE:credsDB

will cause only credsDB to be marked as a credentials db when it is created.

Is there an application which you think is behaving differently than this? If so, can you
point me at it?

Thanks,
-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, 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