[ http://issues.apache.org/jira/browse/DERBY-857?page=all ]
Rick Hillegas updated DERBY-857: -------------------------------- Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. > LDAP user authentication fails under a security manager > ------------------------------------------------------- > > Key: DERBY-857 > URL: http://issues.apache.org/jira/browse/DERBY-857 > Project: Derby > Issue Type: Bug > Components: Security > Affects Versions: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.2.1.6 > Reporter: Daniel John Debrunner > Fix For: 10.2.3.0 > > > 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. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira