[
https://issues.apache.org/jira/browse/OAK-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15670619#comment-15670619
]
Alex COLLIGNON commented on OAK-3626:
-------------------------------------
While I agree with the outcome, I don't think resolved is the correct
resolution for this issue. I would rather see it as won't fix. Not sure you can
change it now, though.
As far as I can see, RFC 227 (ConfigAdminUpdates) is actively edited and still
in draft. I was wondering if we should already test some implementation in
order to evaluate the work required to incorporate this in Oak. I guess that
would require the oak team to maintain an internal release until approval of
the spec, correct ?
> 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)
