[
https://issues.apache.org/jira/browse/OAK-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15673715#comment-15673715
]
angela commented on OAK-3626:
-----------------------------
my understanding based on the discussion with you and [~asanso] is that there
is no need for extra code or internal releases within Oak. however, it might be
worth updating the documentation and optionally adding some example stub to the
exercise section in order to augment understanding of the holistic approach as
possible with RFC 227 compared to an attempt to address the same type of issues
with every single module defining some sort of sensitive OSGi configuration
properties.
> Provide bind credentials callback
> ---------------------------------
>
> Key: OAK-3626
> URL: https://issues.apache.org/jira/browse/OAK-3626
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: auth-ldap
> Reporter: Tobias Bocanegra
>
> The ldap identity provider reads the admin bind credentials from the given
> config which might originate from a un-encrypted source (eg. osgi config).
> in order to facilitate secure provisioning of the bind credentials, the ldap
> idp should offer some sort of credentials provider callback.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
