[ https://issues.apache.org/jira/browse/DERBY-5741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas reassigned DERBY-5741:
------------------------------------
Assignee: Rick Hillegas
> Native user authentication: improve checking of syntax
> ------------------------------------------------------
>
> Key: DERBY-5741
> URL: https://issues.apache.org/jira/browse/DERBY-5741
> Project: Derby
> Issue Type: Improvement
> Components: Services
> Affects Versions: 10.9.0.0
> Reporter: Dag H. Wanvik
> Assignee: Rick Hillegas
> Priority: Minor
> Attachments: derby-5741-01-aa-percolateDerbyErrorUp.diff, repro2.sh
>
>
> Trying to set derby.authentication.provider to "NATIVE:" correctly gives an error message
complaining about the syntax:
> "ERROR XCY05: Invalid setting of the derby.authentication.provider property. This property
cannot be set to NATIVE::LOCAL unless credentials for the database owner have been stored
in the database using the SYSCS_UTIL.SYSCS_CREATE_USER procedure."
> Trying to set it as "NATIVE" (no trailing colon) does not treat this the value as a malformed
NATIVE authentication specification. This leads to it being interpreted as a used defined
authentication class, so when I attempt to connect after disconnection from the database I
see:
> ERROR XJ040: Failed to start database 'cred' with class loader sun.misc.Launcher$AppClassLoader@18d107f,
see the next exception for details.
> ERROR XJ001: Java exception: 'NATIVE: java.lang.ClassNotFoundException'.
> Another thing is that the error message in the first place is out of date now: we never
shoudl be setting "NATIVE::LOCAL" explicitly, it id does once the first user is created according
to version 7.0 of the spec. See DERBY-5742.
--
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
|