[DERBY-4990] Documentation should state a custom security policy being required to use LDAP in conjunction with network driver

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 10.8.1.2
• Component/s: Documentation
• Bug behavior facts: Security
• Assignee: Camilla Haase
• Reporter: Thomas Hill
• Created: 29/Jan/11 12:29
• Updated: 18/Jul/11 19:59
• Resolved: 24/Feb/11 14:32

Description

The documentation is lacking a statement that defining and using a >custom< security manager template is required when wanting to use LDAP authorization provider in conjunction with the network driver client. driver. Otherwise, i.e. just using the default security policy will lead to socket permission errors. Details on which permission exactely needs to be granted to which code base would be very helpful.

Chapter 'Running Derby under a security manager', section 'granting permissions to Derby' in the Developer's guide seems a good place to mention the permission java.net.SocketPermission as optional, but required to be set when wanting to use LDAP authorization in conjunction with the network client driver and defining the authorisation provider properties as system-level properties.

Adding this to the documentation and preferrably also providing some more guidance seems desirable as migrating off the builtin user system to LDAP is strongly recommened and the documentation has explicit statements about security risks otherwise incurred.

I also realized that the template included in the documentation at http://db.apache.org/derby/docs/10.7/adminguide/tadminnetservbasic.html and the default template included in 10.7.1.1 software are no longer in sync.

Issue Links

• relates to: DERBY-4989 LDAP authentication not working when using network client driver and database level properties
• relates to: DERBY-4991 The derby security policy in the Admin Guide is stale.
• relates to: DERBY-3712 Security documentation should state that your java security policy needs to grant you permission to connect to the ldap server if you are using ldap based authentication