Package: django-crowd-sso
django-crowd-ssoSimple Atlassian CROWD authentication backend for Django with SSO
supportConfiguration:Put a CROWD configuration in yoursettings.py:CROWD = {
    'url': 'http://your.crowd.url:port/crowd/rest',         # your CROWD rest API url
    'app_name': 'your-registered-crowd-application-name',   # appname, registered with CROWD
    'password': 'application-password',                     # correct password for provided appname
    'superuser': False,                                     # if True makes CROWD-imported users superusers
    'staffuser': False,                                     # if True makes CROWD-imported users staffuser
    'validation':'10.11.40.34',                             # The ipaddress the Crowd server is responding to
    'sso': False,                                           # TRurn on SSO
    'blocked_creation_domains': ['@example.org'],           # Domains not allowed to be created in the local db
    'crowd_group': 'CrowdUser',                             # Group that all imported users are placed in
    'DTS_not_use_public_schema': False                      # If DTS is installed don't save users and groups in Public schema
}Addcrowd.CrowdBackendin yourAUTHENTICATION_BACKENDSsettings
list. Put it first so that password are only kept in CROWD:AUTHENTICATION_BACKENDS = (
    'crowd.backends.CrowdBackend'
    'django.contrib.auth.backends.ModelBackend',
)Addcrowd.middleware.CrowdMiddlewareto the MiddlewareMIDDLEWARE_CLASSES = (
...
          'crowd.middleware.CrowdMiddleware',
...
)AUTHENTICATION_BACKENDS list to make sure you always start with crowd
authentication before falling over to a local account.simple test:py.testTox test:toxtest currently does not cover the SSORelease NotesVersion 0.57Added support for Django Tenant Schema (django-tenant-schemas) Will
create crowd_group in the public schema if DTS is installed, unless
setting NotPublicSchema == TrueVersion 0.56Add users “Pulled” from crowd to the group defined in crowd_group,
default “CrowdUser” New setting ‘disallowed_creation_domains’:
[‘@wfp.org’]New For version 0.52Added disallowed emails to the import first version hardcoded
@example.org, will be a setting in futureany email with @wfp.org but not in crowd will be in the disallowed listexample of useUser with emaila@b.cis already user ‘a’ in the local db as a django
created userUser with emailb@c.cis already user ‘b’ in the local db as a
imported user from CrowdUser with emailc@a.bis no already user in the local db but exists
in Crowd so it will be imported as user ‘c’User with emaild@e.fis not in local db nor in CrowdUser with emaile@example.orghas a domain that is on the disallowed
listfrom crowd.backends import import_users_from_email_list

        emails = ["a@b.c", "b@c.c", "c@a.b", "d@e.f","e@example.org"]
        added_or_found, not_found, not_alowed = import_users_from_email_list(emails)
        print(added_or_found)
        print(not_found)
        print(not_allowed)Resulting printout:['a','b','c']

['d@e.f']

['e@example.org']Credits:Originally written for Django v1.3 by Konstantin J. Volkovkonstantin-j-volkov@yandex.ruat 12.07.2012Refactored, put together and tested with Django v1.4 by Grigoriy Beziukgbezyuk@gmail.comat 27.08.2012Refactored, updated for Django 1.9 and added SSO and other features by
Tobias Carlandertobias.carlander@wfp.orgat 2015/03/25