db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-857) LDAP user authentication fails under a security manager
Date Fri, 19 Oct 2007 17:24:50 GMT

    [ https://issues.apache.org/jira/browse/DERBY-857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536279

Daniel John Debrunner commented on DERBY-857:

Minor question on the code change (revision 586052).

Is there any reason for creating two extra methods, rather than performing the code in-line
(which is the typical Java pattern) for the priv-blocks?

> LDAP user authentication fails under a security manager
> -------------------------------------------------------
>                 Key: DERBY-857
>                 URL: https://issues.apache.org/jira/browse/DERBY-857
>             Project: Derby
>          Issue Type: Bug
>          Components: Security
>    Affects Versions:,,,,
>            Reporter: Daniel John Debrunner
>            Assignee: Kathey Marsden
>         Attachments: derby-857_diff.txt
> Running the test jdbcapi/secureUsers1.sql with a security manager results in:
> > ERROR 08004: Connection refused : javax.naming.CommunicationException: noSuchMachine:389
[Root exception is java.security.AccessControlException: access denied (java.net.SocketPermission
noSuchMachine resolve)]
> Adding this permission to the policy file has no effect. which means a priv block is
required around the LDAP call.
> permission java.net.SocketPermission "noSuchMachine", "resolve";

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

View raw message