Comments on: Brainstorm: Improving user management in Plone http://jstahl.org/archives/2009/01/06/brainstorm-improving-user-management-in-plone/ Politics, the environment, technology, activism. And stuff. Wed, 02 May 2012 15:47:52 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Souheil "trollfot" Chelfouh http://jstahl.org/archives/2009/01/06/brainstorm-improving-user-management-in-plone/comment-page-1/#comment-393593 Souheil "trollfot" Chelfouh Sun, 11 Jan 2009 02:36:54 +0000 http://blogs.onenw.org/jon/?p=1654#comment-393593 <p>I can only agree with you. User management has been a shame on Plone for years now and it's time to get things moving. I wish to emphasis the poor LDAP plugins state and the fact they rely on half cooked project and ageing ones, such as LDAPMultiPlugin and other very old, uncomplete and erratic *UserFolders.</p> <p>I'm currently working on a big project that made me think a lot about all these issues and i'm developing a new kind of user management based on my homemade content type system, called spear and membrane. Membrane is soon to be replace by another PAS module, but you can already have a look at transition.org : http://tracker.trollfot.org/browser/projects/transition</p> I can only agree with you. User management has been a shame on Plone for years now and it’s time to get things moving. I wish to emphasis the poor LDAP plugins state and the fact they rely on half cooked project and ageing ones, such as LDAPMultiPlugin and other very old, uncomplete and erratic *UserFolders.

I’m currently working on a big project that made me think a lot about all these issues and i’m developing a new kind of user management based on my homemade content type system, called spear and membrane. Membrane is soon to be replace by another PAS module, but you can already have a look at transition.org : http://tracker.trollfot.org/browser/projects/transition

]]> By: Patrick Shaw http://jstahl.org/archives/2009/01/06/brainstorm-improving-user-management-in-plone/comment-page-1/#comment-393584 Patrick Shaw Wed, 07 Jan 2009 17:51:36 +0000 http://blogs.onenw.org/jon/?p=1654#comment-393584 <p>Jon,</p> <p>Pretty much every one of my customers wants to use their email address as their login name - I'd add that to the feature list if I could!</p> Jon,

Pretty much every one of my customers wants to use their email address as their login name – I’d add that to the feature list if I could!

]]> By: Chris Shenton http://jstahl.org/archives/2009/01/06/brainstorm-improving-user-management-in-plone/comment-page-1/#comment-393583 Chris Shenton Wed, 07 Jan 2009 15:52:16 +0000 http://blogs.onenw.org/jon/?p=1654#comment-393583 <p>The LDAP config needs to be config-able with a file, template, buildout variables or some such; the current PloneLDAP config can only be done through the web (or excruciating AppInstall contortions) which foils automated deployment and testing of sites; it's not genericsetup-able.</p> <p>Many government sites have password policy requirements such as strength (easy), max password duration, prevent reuse of past N passwords, lockout after M failures, etc. This may be a bit out of scope of what Plone should do, versus the authentication system, but might help get Plone in the door of .gov and other large orgs with similar security policies.</p> The LDAP config needs to be config-able with a file, template, buildout variables or some such; the current PloneLDAP config can only be done through the web (or excruciating AppInstall contortions) which foils automated deployment and testing of sites; it’s not genericsetup-able.

Many government sites have password policy requirements such as strength (easy), max password duration, prevent reuse of past N passwords, lockout after M failures, etc. This may be a bit out of scope of what Plone should do, versus the authentication system, but might help get Plone in the door of .gov and other large orgs with similar security policies.

]]>