You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Filipe Manana (JIRA)" <ji...@apache.org> on 2010/02/13 22:18:27 UTC
[jira] Created: (COUCHDB-653) Extensible password storage
Extensible password storage
---------------------------
Key: COUCHDB-653
URL: https://issues.apache.org/jira/browse/COUCHDB-653
Project: CouchDB
Issue Type: Improvement
Components: HTTP Interface, Infrastructure
Reporter: Filipe Manana
Fix For: 0.11
As it has been discussed in the @dev mailing list, CouchDB should be configurable to use customizable password storage/hashing schemes.
Brian Candler suggested the support for the OpenLDAP schemes for example.
>From the Auth roadmap mail chain:
"1) Extensible password storage.
Thanks Brian Candler for the links to the OpenLDAP style of storage. I
think we should do this asap so we don't have to worry about backwards
compatibility with the current storage mechanism until the end of
time. The relevant message:
http://permalink.gmane.org/gmane.comp.db.couchdb.devel/7588"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (COUCHDB-653) Extensible password storage
Posted by "Filipe Manana (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Filipe Manana updated COUCHDB-653:
----------------------------------
Attachment: couchdb-extensible-passwd-storage-trunk.patch
The following patch adds support for an extensible password storage scheme, and it implements also 4 of the OpenLDAP passwords storage schemes.
The relevant excerpt of config.ini file is:
[couch_httpd_auth]
password_hash_scheme = -hashed- ; default scheme to use when hashing passwords
password_validators = {couch_httpd_auth, couch_validate_password}, {couch_httpd_auth, openldap_validate_password}
[password_hash_creators]
; scheme = {module, function}
-hashed- = {couch_httpd_auth, couch_hash_password}
{SSHA} = {couch_httpd_auth, openldap_hash_password}
{SHA} = {couch_httpd_auth, openldap_hash_password}
{SMD5} = {couch_httpd_auth, openldap_hash_password}
{MD5} = {couch_httpd_auth, openldap_hash_password}
> Extensible password storage
> ---------------------------
>
> Key: COUCHDB-653
> URL: https://issues.apache.org/jira/browse/COUCHDB-653
> Project: CouchDB
> Issue Type: Improvement
> Components: HTTP Interface, Infrastructure
> Reporter: Filipe Manana
> Fix For: 0.11
>
> Attachments: couchdb-extensible-passwd-storage-trunk.patch
>
>
> As it has been discussed in the @dev mailing list, CouchDB should be configurable to use customizable password storage/hashing schemes.
> Brian Candler suggested the support for the OpenLDAP schemes for example.
> From the Auth roadmap mail chain:
> "1) Extensible password storage.
> Thanks Brian Candler for the links to the OpenLDAP style of storage. I
> think we should do this asap so we don't have to worry about backwards
> compatibility with the current storage mechanism until the end of
> time. The relevant message:
> http://permalink.gmane.org/gmane.comp.db.couchdb.devel/7588"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (COUCHDB-653) Extensible password storage
Posted by "Noah Slater (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Noah Slater updated COUCHDB-653:
--------------------------------
Fix Version/s: (was: 0.11)
0.12
> Extensible password storage
> ---------------------------
>
> Key: COUCHDB-653
> URL: https://issues.apache.org/jira/browse/COUCHDB-653
> Project: CouchDB
> Issue Type: Improvement
> Components: HTTP Interface, Infrastructure
> Reporter: Filipe Manana
> Fix For: 0.12
>
> Attachments: couchdb-extensible-passwd-storage-trunk.patch
>
>
> As it has been discussed in the @dev mailing list, CouchDB should be configurable to use customizable password storage/hashing schemes.
> Brian Candler suggested the support for the OpenLDAP schemes for example.
> From the Auth roadmap mail chain:
> "1) Extensible password storage.
> Thanks Brian Candler for the links to the OpenLDAP style of storage. I
> think we should do this asap so we don't have to worry about backwards
> compatibility with the current storage mechanism until the end of
> time. The relevant message:
> http://permalink.gmane.org/gmane.comp.db.couchdb.devel/7588"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (COUCHDB-653) Extensible password storage
Posted by "Paul Joseph Davis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Joseph Davis updated COUCHDB-653:
--------------------------------------
Skill Level: Regular Contributors Level (Easy to Medium)
> Extensible password storage
> ---------------------------
>
> Key: COUCHDB-653
> URL: https://issues.apache.org/jira/browse/COUCHDB-653
> Project: CouchDB
> Issue Type: Improvement
> Components: HTTP Interface, Infrastructure
> Reporter: Filipe Manana
> Fix For: 0.12
>
> Attachments: couchdb-extensible-passwd-storage-trunk.patch
>
>
> As it has been discussed in the @dev mailing list, CouchDB should be configurable to use customizable password storage/hashing schemes.
> Brian Candler suggested the support for the OpenLDAP schemes for example.
> From the Auth roadmap mail chain:
> "1) Extensible password storage.
> Thanks Brian Candler for the links to the OpenLDAP style of storage. I
> think we should do this asap so we don't have to worry about backwards
> compatibility with the current storage mechanism until the end of
> time. The relevant message:
> http://permalink.gmane.org/gmane.comp.db.couchdb.devel/7588"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.