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

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

Thanks, Rick! That worked. I didn't try to see what would happen if I'd tried 
to create a user other than APP, since APP owned the only schema with data. 
Without an authentication provider, would there have been an error? 

 jdench 121 =>mv derby.properties notderby.properties
 jdench 122 =>java -jar ../codetrunk/trunk/jars/insane/derbyrun.jar ij
ij version 10.9
ij> connect 'jdbc:derby:testDB';
ij> call SYSCS_UTIL.SYSCS_CREATE_USER('APP', 'app');
0 rows inserted/updated/deleted
ij> select username from sys.sysusers;
USERNAME                                                                        
                                                
--------------------------------------------------------------------------------------------------------------------------------
APP                                                                             
                                                

1 row selected
ij> exit;
 jdench 123 =>mv notderby.properties derby.properties
 jdench 124 =>java -jar ../codetrunk/trunk/jars/insane/derbyrun.jar ij
ij version 10.9
ij> connect 'jdbc:derby:testDB;user=app;password=app';
ij> select * from t1;
N          
-----------

0 rows selected
ij> insert into t1 values(33);
1 row inserted/updated/deleted
ij> select * from t1;
N          
-----------
33
1 row selected
ij> values 
SYSCS_UTIL.SYSCS_get_database_property('derby.authentication.provider');
1                                                                               
                                                
--------------------------------------------------------------------------------------------------------------------------------
NATIVE::LOCAL                                                                   
                                                

1 row selected

                
> 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

        

Reply via email to