You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Andreas Kyrmegalos (JIRA)" <ji...@apache.org> on 2008/06/05 23:30:45 UTC
[jira] Commented: (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
[ https://issues.apache.org/jira/browse/DERBY-3712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602798#action_12602798 ]
Andreas Kyrmegalos commented on DERBY-3712:
-------------------------------------------
I'd like to point out that Myrna van Lunteren stated in a follow-up to said e-mail that 'connect, resolve' covers more test cases. Apparently when the ldap host is declared as a domain name it has to be resolved against its IP address. So, a more complete approach would be to grant a 'connect, resolve' permission to the ldap host and most likely to the dns server host as well.
> 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
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3712
> URL: https://issues.apache.org/jira/browse/DERBY-3712
> Project: Derby
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 10.4.1.3
> Reporter: Rick Hillegas
>
> Andreas Kyrmegalos raised this issue in an email message: http://www.nabble.com/shutdown-fails-when-basic-security-policy-is-active-and-authentication-is-ldap-based-td17674473.html#a17674473
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.