node.ext.ugm 0.9.10

Node-based user and group management

User and group management

node.ext.ugm provides an API for node based managing of users and groups.

See node.ext.ugm.interfaces for a description of the API.

A file based default implementation can be found at node.ext.ugm.file.

Base objects for writing UGM implementations can be found at node.ext.ugm._api.

For more information on nodes see node package.

For more information on plumbing see plumber package.

Python Versions

• Python 2.7, 3.3+, pypy

• May work with other versions (untested)

Contributors

• Robert Niederreiter

• Florian Friesdorf

Changes

0.9.10 (2019-11-07)

• Also derive IPrincipals interface from node.interfaces.IInvalidate. Implement invalidate function on FileStorage. [rnix, 2019-06-30]

• Persist users file on password change. [rnix, 2019-06-30]

• Add UserAttributes and GroupAttributes classes deriving from FileAttributes and handle reserved attributes expected by cone.ugm there. This might change in future. [rnix, 2019-06-27]

• File based principals support binary attributes now. [rnix, 2019-06-26]

• Return all principals in file based UGM imlementation if no search criteria given. [rnix, 2019-06-26]

• Remove superfluous configure.zcml file. [rnix, 2019-04-13]

• Remove cone.app main hook for initializing file based UGM implementation. This is handled in cone.app itself as of version 1.0 [rnix, 2019-03-28]

0.9.9

• node.ext.ugm.file.FileStorage no longer provides unicode_keys and unicode_values, files are always read and written encoded by encoding defined at node.ext.ugm.file.ENCODING, keys and values are always decoded to unicode on read. [rnix, 2017-06-07]

• Python 3 Support. [rnix, 2017-06-07]

0.9.8

• Fix bug where non related principal data has been overwritten when adding principal on partial loaded ugm tree. [rnix, 2015-04-12]

• Also delete user and group corresponding data if user or group is deleted. [rnix, 2015-04-11]

• Fix node.ext.ugm.file.UsersBehavior.passwd behavior. [rnix, 2015-04-11]

0.9.7

• Create user and group data directories recursiv if not exists. [rnix, 2014-12-02]

0.9.6

• Encode plain passwd for comparing with hash. [rnix, 2014-09-10]

0.9.5

• Use plumbing decorator instead of plumber metaclass. [rnix, 2014-08-01]

0.9.4

• Use better password hashing for file based default UGM implementation. Warning - all existing passwords in user table do not work any longer and must be reset. [rnix, 2014-06-13]

0.9.3

• Rename parts to behaviors. [rnix, 2012-07-29]

• adopt to node 0.9.8. [rnix, 2012-07-29]

• Adopt to plumber 1.2. [rnix, 2012-07-29]

• Add User.group_ids. [rnix, 2012-07-26]

0.9.2

• Remove outdated stuff. [rnix, 2012-05-18]

• Use zope.interface.implementer instead of zope.interface.implements. [rnix, 2012-05-18]

0.9.1

• add Users.id_for_login. [rnix, 2012-01-18]

• Implement search function for file based UGM as described in interface. [rnix, 2011-11-22]

• Adopt application startup hook for cone.ugm only setting auth implementation if explicitely defined. [rnix, 2011-11-21]

0.9

• make it work [rnix, chaoflow]

License

Copyright (c) 2011-2019, BlueDynamics Alliance, Austria All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

• Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

• Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

• Neither the name of the BlueDynamics Alliance nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY BlueDynamics Alliance AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL BlueDynamics Alliance BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.