You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2012/08/07 19:00:24 UTC
[jira] [Created] (JCR-3405) Improvements to user management
implementation
angela created JCR-3405:
---------------------------
Summary: Improvements to user management implementation
Key: JCR-3405
URL: https://issues.apache.org/jira/browse/JCR-3405
Project: Jackrabbit Content Repository
Issue Type: Bug
Components: jackrabbit-core, security
Reporter: angela
Assignee: angela
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JCR-3405) Improvements to user management
implementation
Posted by "angela (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13430433#comment-13430433 ]
angela commented on JCR-3405:
-----------------------------
already committed (jira was not responsive) at revision: 1370326
- move configuration code to separate UserManagerConfig
- rename impl specific public method getGroupMembershipSplitSize to getMemberSplitSize
- add method hasMemberSplitSize and replace usage of getGroupMembershipSplitSize() > 0 (and similar)
- remove old class name from javadoc in NodeCreationTest
> Improvements to user management implementation
> ----------------------------------------------
>
> Key: JCR-3405
> URL: https://issues.apache.org/jira/browse/JCR-3405
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core, security
> Reporter: angela
> Assignee: angela
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JCR-3405) Improvements to user management
implementation
Posted by "Lars Krapf (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Krapf updated JCR-3405:
----------------------------
Attachment: patch.jcr.3405.txt
The attached patch backports the trunk improvements (and some additional changes for the getGroupMembershipSplitSize fix [r1393405] ) to 2.4.
> Improvements to user management implementation
> ----------------------------------------------
>
> Key: JCR-3405
> URL: https://issues.apache.org/jira/browse/JCR-3405
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core, security
> Reporter: angela
> Assignee: angela
> Fix For: 2.5.2
>
> Attachments: patch.jcr.3405.txt
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JCR-3405) Improvements to user management
implementation
Posted by "angela (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
angela updated JCR-3405:
------------------------
Issue Type: Improvement (was: Bug)
> Improvements to user management implementation
> ----------------------------------------------
>
> Key: JCR-3405
> URL: https://issues.apache.org/jira/browse/JCR-3405
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core, security
> Reporter: angela
> Assignee: angela
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (JCR-3405) Improvements to user management
implementation
Posted by "angela (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
angela resolved JCR-3405.
-------------------------
Resolution: Fixed
Fix Version/s: 2.5.2
> Improvements to user management implementation
> ----------------------------------------------
>
> Key: JCR-3405
> URL: https://issues.apache.org/jira/browse/JCR-3405
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core, security
> Reporter: angela
> Assignee: angela
> Fix For: 2.5.2
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JCR-3405) Improvements to user management
implementation
Posted by "angela (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13430511#comment-13430511 ]
angela commented on JCR-3405:
-----------------------------
Revision: 1370420
- add PasswordUtility for creating + comparing passwords
- UserManagerImpl: some config options related to password hashing
> PARAM_PASSWORD_HASH_ALGORITHM: the algorithm to use (default: SHA-256)
> PARAM_PASSWORD_HASH_ITERATIONS: number of iterations (default: 1000)
currently the salt size is not configurable. that could be added easily if required.
- some improvement to handling of plaintxt passwords starting with {algorithm}. as of rev. 1370420 all API
methods taking a plaintxt password treat it as plaintxt pw and thus force hashing. this contrasts to
UserImporter which is expected to deal with password strings extracted from the repo before and thus
doesn't enforce an extra hashing step.
so far no performance test were made if changing the default hashing has an impact on login. i would
expect that with increasing number of iterations.
> Improvements to user management implementation
> ----------------------------------------------
>
> Key: JCR-3405
> URL: https://issues.apache.org/jira/browse/JCR-3405
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core, security
> Reporter: angela
> Assignee: angela
> Fix For: 2.5.2
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira