jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-3626) Provide bind credentials callback
Date Fri, 13 Nov 2015 07:54:11 GMT

    [ https://issues.apache.org/jira/browse/OAK-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15003674#comment-15003674
] 

angela commented on OAK-3626:
-----------------------------

IMHO this is a new feature.
an alternative way to address this (instead of the callback) could be to introduce a crypto
module (maybe just basic interfaces) in Oak and make the encryption of the password depending
on the availability of a service implementing this.... obviously this would only be sensible
if we see generic need for something like this (e.g. thinking of automatic encryption of properties
in a {{CommitEditor}} based on the presence of dedicated mixin type).

> 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)

Mime
View raw message