db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (DERBY-2435) network server boot fails indicating authentication must be set up even when authentication is fully defined in derby.properties
Date Mon, 19 Mar 2007 14:24:32 GMT

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

Rick Hillegas reassigned DERBY-2435:
------------------------------------

    Assignee:     (was: Rick Hillegas)

Unassigning. I believe this issue can be closed.

> network server boot fails indicating authentication must be set up even when authentication
is fully defined in derby.properties
> --------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2435
>                 URL: https://issues.apache.org/jira/browse/DERBY-2435
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Server, Security
>    Affects Versions: 10.3.0.0
>            Reporter: Daniel John Debrunner
>            Priority: Critical
>         Attachments: derby-2435-01.diff
>
>
> Booting the server using the default to install a security manager fails even when the
derby.properties is in the current directory with these contents.
> derby.connection.requireAuthentication=true
> derby.authentication.provider=BUILTIN
> derby.user.SA=sapwd
> derby.user.MARY=marypwd
> The documentation on authentication indicates this is the preferred way to setup authentication
for a server machine.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message