[jira] [Closed] (DERBY-5657) Message XCY05 for NATIVE authentication is (too?) complex

["Kristian Waagan (Closed) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DERBY-5657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kristian Waagan closed DERBY-5657.
----------------------------------

    Assignee: Rick Hillegas

Thanks, Rick.
Closing issue.
                
> Message XCY05 for NATIVE authentication is (too?) complex
> ---------------------------------------------------------
>
>                 Key: DERBY-5657
>                 URL: https://issues.apache.org/jira/browse/DERBY-5657
>             Project: Derby
>          Issue Type: Improvement
>          Components: Services
>    Affects Versions: 10.9.0.0
>            Reporter: Kristian Waagan
>            Assignee: Rick Hillegas
>            Priority: Minor
>             Fix For: 10.9.0.0
>
>         Attachments: derby-5657-01-aa-splitMessage.diff
>
>
> The error message XCY05 is rather complex:
> Invalid change of the derby.authentication.provider property. Once set to NATIVE authentication, this property cannot be changed. NATIVE::LOCAL is the only NATIVE value accepted by derby.authentication.provider. 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.
> I'd be in favor of simplifying this error message if possible, especially raising a more specific message for the error condition when the DBO hasn't been added as a user.
> Further, it was not clear to me that the information about derby.authentication.provider applies when setting it as a database property only.
> Is this message trying to describe three problem scenarios?
>  a) Turning off NATIVE authentication is forbidden.
>  b) Specifying an invalid value for derby.authentication.provider when set as a database property.
>  c) Missing credentials for the DBO.

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