Saravanan666/pypi-org huggingface dataset:
Package: django-allauth-2f2a
django-allauth-2f2ais a port ofdjango-allauth-2fathat addstwo-factor authenticationtodjango-allauthand intends to
continue active development of the code.  The current goals include
generatingSVGcodes as files to allow strictercontent security
policies, configuration of form classes used by the app to allow
subclassing forms for use withdjango-crispy-forms, and improvedCIand testing.FeaturesAddtwo-factor authenticationviews and workflow todjango-allauth.Support Authenticator apps via aQR codewhen enabling2FA.Support single-use back-up codes.Compatibilitydjango-allauth-2f2awill only maintain compatibility with supported
versions ofDjangoandpythonand recent, secure versions ofdjango-allauth, anddjango-otp, currently:Python3.6-3.9.Django2.2, 3.2.django-allauth0.44.0 and newer.django-otp1.0.0 and newer.Running TestsCurrently, tests can be run using the standard Django testing facility:pythonmanage.pytestor by running tox:toxProject tests will be moved to pytest in the future.Running the Test ProjectThe test project can also be used as a minimal example using the following:# Migrate the SQLite database first.DJANGO_SETTINGS_MODULE=tests.settingspythonmanage.pymigrate# Run the server with debug.DJANGO_SETTINGS_MODULE=tests.settingspythonmanage.pyrunserver# Run the shell.DJANGO_SETTINGS_MODULE=tests.settingspythonmanage.pyshellContributingCreate an issue/pull request.  Check the roadmap for ideas.All tox targets should pass.  That includes all tests in all
supported environments and all the linting checks (black, isort,
flake8 and flake8-docstrings).Test coverage should be 100%.  New features should have new tests.Roadmapimplement other OTP/2FA methods in addition to TOTP (seehttps://github.com/valohai/django-allauth-2fa/issues/23)staticHOTPYubiKeyTwilioclarify code commentsclarify documentation and improve examplespublish documentationinclude docstrings in published documentationcomplete meaningful test coverage (make sure the 100% is not just the number)generateSVGcodes as files (completed 0.9.0)allow configurable form classes (make your formscrispy; completed 0.9.0)complete test coverage (completed 0.9.0)requireblack,flake8-docstrings,pydocstyle,isort,pccc, andpre-commit(completed 0.8.1)Authordjango-allauth-2fawas originally created byVíðir Valberg Guðmundsson (@valberg)ofPercipient Networks.  All modifications after the port todjango-allauth-2f2aare created and maintained byJeremy A GrayatFQS.
Package: django-allauth-2fa
django-allauth-2fa addstwo-factor authenticationtodjango-allauth.
django-allauth is a set ofDjangoapplications which help with
authentication, registration, and other account management tasks.Source codehttp://github.com/percipient/django-allauth-2faDocumentationhttps://django-allauth-2fa.readthedocs.io/FeaturesAddstwo-factor authenticationviews and workflow todjango-allauth.Supports Authenticator apps via a QR code when enabling 2FA.Supports single-use back-up codes.Compatibilitydjango-allauth-2fa attempts to maintain compatibility with supported versions of
Django, django-allauth, and django-otp.Current versions supported together is:Djangodjango-allauthdjango-otpPython3.20.53.01.13.7, 3.8, 3.9, 3.104.00.53.01.13.8, 3.9, 3.10, 3.114.10.53.01.13.8, 3.9, 3.10, 3.114.20.53.01.13.8, 3.9, 3.10, 3.11Contributingdjango-allauth-2fa was initially created byVíðir Valberg Guðmundsson (@valberg), was maintained byPercipient Networksfor many years, and is now maintained byValohai. Please feel free to contribute if you find
django-allauth-2fa useful!Check for open issues or open a fresh issue to start a discussion
around a feature idea or a bug.If you feel uncomfortable or uncertain about an issue or your changes,
feel free to emailsupport@percipientnetworks.comand we will happily help you.Forkthe repositoryon GitHub to start making your changes to themainbranch (or branch off of it).Write a test which shows that the bug was fixed or that the feature
works as expected.Send a pull request and bug the maintainer until it gets merged and
published.Running testsTests can be run using [pytest](https://docs.pytest.org/en/6.2.x/).pipinstall-rrequirements-test.txtpy.testRunning the test projectThe test project can also be used as a minimal example using the following:# Migrate the SQLite database first.DJANGO_SETTINGS_MODULE=tests.settingspythonmanage.pymigrate# Run the server with debug.DJANGO_SETTINGS_MODULE=tests.settingspythonmanage.pyrunserver_plus# Run the shell.DJANGO_SETTINGS_MODULE=tests.settingspythonmanage.pyshell_plus
Package: django-allauth-bootstrap
Twitter Bootstrap layout fordjango-allauth.NoteThe current version 0.2 supportsDjango’sregistration and
login viadjango-allauth. Support forsocial accountswill be added in one of the upcoming versions.RequirementsPython 2.7 or >=3.3.Django >=1.9InstallationInstallation via:pip install django-allauth-bootstrapThe templates extendbase.html, so thetemplatesfolder of the
project should provide one, together with the Twitter Bootstrap and a JQuery
library.Then add'bootstrapform'and'allauth_bootstrap'toINSTALLED_APPS,before'allauth'.  The order is important because
following apps are overwritten:INSTALLED_APPS = [
    # ...
    'django.contrib.sites',  # For ``allauth``.

    'bootstrapform',
    'allauth_bootstrap',
    'allauth',
    'allauth.account',
    # ...
]For allauth itself, remember to add the following settings:TEMPLATES = [
    {
        'BACKEND': 'django.template.backends.django.DjangoTemplates',
        'DIRS': [],
        'APP_DIRS': True,
        'OPTIONS': {
            'context_processors': [
                # Already defined Django-related contexts here

                # `allauth` needs this from django
                'django.template.context_processors.request',
            ],
        },
    },
]

SITE_ID = 1

LOGIN_REDIRECT_URL = '/'Example ProjectThe example project can be run to have a quick look and to check out a
running setup. Download the source files and run:virtualenv -p /usr/bin/python3 ~/myenv
source ~/myenv/bin/activate
pip install -r requirements.txt
./manage.py migrate
./manage.py runserverCustomizationTo use custom templates, there are two ways to accomplish that:Overwrite a template attemplates/accountto replace them completely.Inherit a template attemplates/accountto overwrite only one or more
of its blocks. Defining a custom URL pointing at the custom template is
necessary then.
Package: django-allauth-cas
CAS support fordjango-allauth.RequirementsDjango 1.8 → 2.0Dependenciesdjango-allauthpython-cas: CAS client libraryNoteTests only target the latest allauth version compatible for each Django version
supported:Django 1.9 with django-allauth 0.32.0;Django 1.8, 1.10, 1.11, 2.0 with the latest django-allauth.If you have any problems at use or think docs can be clearer, take a little
time to open an issue and/or a PR would be welcomed ;-)AcknowledgmentsThis work is strongly inspired by theOAuth2 support of django-allauth.InstallationInstall the python packagedjango-allauth-cas. For example, using pip:$pipinstalldjango-allauth-casAdd'allauth_cas'toINSTALLED_APPS.
Package: django-allauth-d120
django-allauth-d120django-allauth-d120 is a provider forallauthto integrate d120
accounts into django projects. It therefor provides a wrapper around the allauth OAuth 2.0 provider and connects it
with thekeycloakOAuth 2.0 endpoint. The app allows to synchronize the groups of a
user from keycloak to your django project.InstallationInstall django-allauth-d120 with pip e.g.pip install django-allauth django-allauth-d120Add the following apps to the installedINSTALLED_APPSin thesettings.py:'django.contrib.sites','allauth','allauth.account','allauth.socialaccount','allauth_d120_provider',Configure the Authentication backends in thesettings.py:AUTHENTICATION_BACKENDS=(# Needed to login by username in Django admin, regardless of `allauth`'django.contrib.auth.backends.ModelBackend',# `allauth` specific authentication methods, such as login by e-mail'allauth.account.auth_backends.AuthenticationBackend',)Configure allauth to disable email verification, account sing up outside the sso and
account sign up via the sso in thesettings.py:ACCOUNT_EMAIL_VERIFICATION="none"ACCOUNT_ADAPTER="allauth_d120_provider.account_adapter.DisableSignUpAdapter"SOCIALACCOUNT_ADAPTER="allauth_d120_provider.account_adapter.SocialAccountAdapter"Runmanage.py migrateto create sync the database with the newly installed appsLogin into the Django Admin webinterface to configure the website object. Therefore go to site section and
select the site model e.g. the url ends onadmin/sites/site/whereadmin/is the root path of Django Admin
in your project. Make sure the domain matches the domain your project is running on.Within Django Admin go to the Social Accounts section and select the Social applications model e.g. the url
ends onadmin/socialaccount/socialapp/whereadmin/is the root path of Django Admin in your project.
Add a new instance which usesD120 OAuth 2.0as provider. Please ask fss@ for a Client id and the related Secret Key.Have a look at theinstructions to install allauth.
There might be steps necessary steps that are not mentioned in this instruction.Group SynchronizationYou can create a group synchronization by adding instances of the groupsync Model via Django Admin.
Therefor select the Group Synchronization model in the D120 Autentication Provider section.
The groups synchronize when the user logs into the project.
Package: django-allauth-djrill
This package provides adjango-allauthaccount adapter for sending email utilizing templates stored inMandrill,
thanks to theDjrillpackage.InstallationTo install the latest release:pip install django-allauth-djrillAlternatively, to install the latest development version:pip install https://github.com/obsidiancard/django-allauth-djrill/tarball/masterAmend yourINSTALLED_APPSsetting:INSTALLED_APPS = (
    ...,
    'allauth_djrill',
)Ensure that yourEMAIL_BACKENDis set up to use Djrill:EMAIL_BACKEND = 'djrill.mail.backends.djrill.DjrillBackend'Switch your allauth account adapter:ACCOUNT_ADAPTER = 'allauth_djrill.adapter.DjrillAccountAdapter'If you wish to customize the names of the templates which are called in Mandrill’s system, you can edit theALLAUTH_DJRILL_TEMPLATESsetting. The defaults are:ALLAUTH_DJRILL_TEMPLATES = {
    'account/email/email_confirmation': 'email_confirmation',
    'account/email/email_confirmation_welcome': 'email_confirmation_welcome',
    'account/email/email_confirmation_signup': 'email_confirmation_signup',
    'account/email/password_reset_key': 'password_reset_key',
}
Package: django-allauth-id4me
django-allauth-id4meExtension library for django-allauth to support ID4me (https://id4me.org) as social login provider.Specification referencehttps://gitlab.com/ID4me/documentation/blob/master/id4ME%20Technical%20Specification.adocVersion: 1.0Revision: 02InstallationInstall the package from pippipinstalldjango-allauth-id4meConfigure django-allauth if not yet installedSee documentationConfigure django projectAddallauth_id4metoINSTALLED_APPSin yoursettings.py:INSTALLED_APPS=(...# ... include the providers you want to enable:'allauth_id4me',...)Run migrations in your django projectpythonmanage.pymigrateAdd social client configurationStart your django projectpython.exemanage.pyrunserverlocalhost:8000Open /admin applicationhttp://localhost:8000/admin/Go to Home â€º Social Accounts â€º Social applications and add new application:Provider: ID4meName: the name of your application (will appear on login screen)Client id: wished client_id, may however not be respectedSecret key: not used, fill with dummy valueOpenhttp://localhost:8000/accounts/login/and test the login with ID4me!Template customizationTo present own ID4me login page it is enough to place new template inid4mefolder inside yourtemplatesdictionary namedlogin.html. Minimum required content:<formid="id4me_login_form"class="id4me_login"method="post"action="{% url 'id4me_login' %}">{% csrf_token %}
    {{form.as_p}}<buttontype="submit">Sign In</button></form>CHANGELOG:versiondatechanges0.0.132019-03-05- IMPROVEMENT: setting always state for increased compatibility0.0.122019-03-05- NEW FEATURE: input field to set cookie and remember ID0.0.112019-02-27- BUGFIX: Client registration updated when re-registered
Package: django-allauth-intersis
[![Downloads](https://pypip.in/download/django-allauth-intersis/badge.svg)](https://pypi.python.org/pypi/django-allauth-intersis/)django-allauth-intersis=============OAuth2.0 InterSIS access module for projects using django-allauth.This module allows users of django-allauth to seamlessly integrate InterSIS single sign-on into their Django projects.InterSIS is an in-development, open student-information and single sign-on API spec and implementation.This module will not be suitable for general use until the first official release of the InterSIS API implementation.Installation===============Install the module in your Python distribution or virtualenv:$ pip install django-allauth-intersisAdd the application to your `INSTALLED_APPS`:```INSTALLED_APPS = (...'allauth_intersis',...)```In settings.py:```...INTERSIS_CLIENT_NAME='Example Your Client/Application Name'BASE_INTERSIS_SERVER_URL='https://intersis.example.edu'BASE_INTERSIS_CLIENT_URL='https://example.your_domain.com'...```And in urls.py:```...url(r'^intersis/', include('allauth_intersis.urls')),  # Must come AFTER your allauth.urls line...```Of course, you must also have django-allauth installed. See the django-allauth project homepage for description and instructions:http://www.intenct.nl/projects/django-allauth/Use===Detailed use instructions to follow, upon the first official release of the InterSIS API implementation.Compatibility=============* Django 1.7* Python 2.7, 3.4* Allauth 0.19.0Todo====* Multiple features privately trackedGetting Involved================If you are interested in following the InterSIS project, please contact me (JASchilz) at my listed email address.
Package: django-allauth-james
Integrated set of Django applications addressing authentication,
registration, account management as well as 3rd party (social) account
authentication.Home pagehttp://www.intenct.nl/projects/django-allauth/Source codehttp://github.com/pennersr/django-allauthMailinglisthttp://groups.google.com/group/django-allauthDocumentationhttp://django-allauth.readthedocs.org/en/latest/Stack Overflowhttp://stackoverflow.com/questions/tagged/django-allauthRationaleMost existing Django apps that address the problem of social
authentication focus on just that. You typically need to integrate
another app in order to support authentication via a local
account.This approach separates the worlds of local and social
authentication. However, there are common scenarios to be dealt with
in both worlds. For example, an e-mail address passed along by an
OpenID provider is not guaranteed to be verified. So, before hooking
an OpenID account up to a local account the e-mail address must be
verified. So, e-mail verification needs to be present in both worlds.Integrating both worlds is quite a tedious process. It is definitely
not a matter of simply adding one social authentication app, and one
local account registration app to yourINSTALLED_APPSlist.This is the reason this project got started – to offer a fully
integrated authentication app that allows for both local and social
authentication, with flows that just work.Commercial SupportThis project is sponsored byIntenCT. If you require assistance on
your project(s), please contact us:info@intenct.nl.
Package: django-allauth-jetbrains-hub
django-allauth-jetbrains-hubJetbrains Hub OAuth2 provider for django-allauthInstallationRequirementsdjango-allauth (https://github.com/pennersr/django-allauth)Python Packagepip install django-allauth-jetbrains-hubsettings.pyThe server value in the path request must be set to point to your Jetbrains
hub instance and include the full path to it. For example, if your instance
is athttps://example.com/but you get redirected tohttps://example.com/hub/you should set server tohttps://example.com/hub/.INSTALLED_APPS = (
    ...
    # The following apps are required:
    'django.contrib.auth',
    'django.contrib.sites',

    'allauth',
    'allauth.account',
    'allauth.socialaccount',
     ...
     # Add allauth_microsoft to installed_apps
     'allauth_jetbrains_hub'
     ...
)

SOCIALACCOUNT_PROVIDERS = {
    'jetbrains-hub': {
        'SERVER': 'https://example.com/hub/',
    }
}Post-InstallationCreate service in your hub instanceCreate a service in your hub instance as documentedhere.Open the service in HUB.Set the Redirect URI tohttps://example.com/accounts/jetbrains-hub/login/callback/.Copy your Application ID and click change secret to get a new secret.Enter the Application ID and Secret into the Django Admin interface.ContributorsGary Kramlichgrim@reaperworld.comForked fromgithub.com/schaenzer/django-allauth-microsoft.LicenseMIT License
Package: django-allauth-keycloak-ext
django-allauth-keycloak-ext is a Python package that extends Django-allauth to support security groups configured in Keycloak.FeaturesSupports adding/removing users from Django groups mapped to Keycloak groups during login procedure.Supports mapping Keycloak groups to is_staff and is_superuser flags of Django users.Supports mapping of Keycloak groups to Django ones.InstallationTo install django-allauth-keycloak-ext, run the following command:pipinstalldjango-allauth-keycloak-extUsageOnce you have installed django-allauth-keycloak-ext, you can use it in your Django project by following these steps:Add‘allauth_keycloak_groups’to yourINSTALLED_APPSsetting:INSTALLED_APPS=[# ...'allauth_keycloak_ext',# ...]Configure Django-allauth to use Keycloak Ext as a provider and map flags to Keycloak groups by adding the following settings to yoursettings.pyfile:SOCIALACCOUNT_PROVIDERS={"keycloak_ext":{"KEYCLOAK_URL":"http://localhost:8080","KEYCLOAK_REALM":"master","GROUPS":{"GROUP_TO_FLAG_MAPPING":{"is_staff":["Django Staff","django-admin-role"],"is_superuser":"django-admin-role",},}}}Configure the security groups you want to use in Keycloak and map them to Django groups in yoursettings.pyfile:SOCIALACCOUNT_PROVIDERS={"keycloak_ext":{"KEYCLOAK_URL":"http://localhost:8080","KEYCLOAK_REALM":"master","GROUPS":{..."GROUPS_MAPPING":{"django-admin-role":"django-admin-group","offline_access":"Offline Group",}...},}}Note that the keys of theGROUPS_MAPPINGdictionary should be the names of the security groups you have configured in Keycloak, and the values should be the names of the Django groups you want to map them to.Configure auto creation of the security groups in Django in yoursettings.pyfile:SOCIALACCOUNT_PROVIDERS={"keycloak_ext":{"KEYCLOAK_URL":"http://localhost:8080","KEYCLOAK_REALM":"master","GROUPS":{..."GROUPS_MAPPING":{"django-admin-role":"django-admin-group","offline_access":None,},"GROUPS_AUTO_CREATE":True,},}}Note that you can disable creating of any group by mapping them toNone.Usage Examplehttps://github.com/wonderu/keycloak-django- test applicationLicenseThis package is released under the MIT License.ContributingContributions to this project are welcome. Please submit bug reports
Package: django-allauth-mandrill
This package provides adjango-allauthaccount adapter for sending email utilizing templates stored inMandrill,
thanks to theDjrillpackage.InstallationTo install the latest release:pip install django-allauth-djrillAlternatively, to install the latest development version:pip install https://github.com/obsidiancard/django-allauth-djrill/tarball/masterAmend yourINSTALLED_APPSsetting:INSTALLED_APPS = (
    ...,
    'allauth_djrill',
)Ensure that yourEMAIL_BACKENDis set up to use Djrill:EMAIL_BACKEND = 'djrill.mail.backends.djrill.DjrillBackend'Switch your allauth account adapter:ACCOUNT_ADAPTER = 'allauth_djrill.adapter.DjrillAccountAdapter'If you wish to customize the names of the templates which are called in Mandrill’s system, you can edit theALLAUTH_DJRILL_TEMPLATESsetting. The defaults are:ALLAUTH_DJRILL_TEMPLATES = {
    'account/email/email_confirmation': 'email_confirmation',
    'account/email/email_confirmation_welcome': 'email_confirmation_welcome',
    'account/email/email_confirmation_signup': 'email_confirmation_signup',
    'account/email/password_reset_key': 'password_reset_key',
}
Package: django-allauth-saml2
Django allauth saml2 provider, this provider is based on pysaml2 (https://pysaml2.readthedocs.io/)Quick startAdd “allauth_saml2” to your INSTALLED_APPS setting like this:INSTALLED_APPS = [
    ...
    'allauth_saml2',
]

SOCIALACCOUNT_PROVIDERS = {
    'saml2': {
        # Metadata is required, choose either remote url or local file path
        'METADATA_AUTO_CONF_URL': 'The metadata configuration url',
        'METADATA_LOCAL_FILE_PATH': 'The metadata configuration file path',

        # EntityID populates the Issuer element in authn request Entity ID, optional, url of sp is used when missing
        # 'ENTITY_ID': 'https://mysite.com/saml2_auth/acs/', #

        # 'NAME_ID_FORMAT': FormatString, # Sets the Format property of authn NameIDPolicy element

        # encrypt/sign assertions
        # 'KEY_FILE': 'key.pem path',
        # 'CERT_FILE': 'cert.pem path',

        # 'ACCEPTED_TIME_DIFF':
    }
}CreditsTools used in rendering this package:Cookiecuttercookiecutter-djangopackageHistory0.1.0 (2021-04-30)First release on PyPI.
Package: django-allauth-steemconnect
# django-allauth-steemconnectSteemconnect provider for django-allauth.## Installation```shellpip install django-allauth-steemconnect```## Quick start1. Add "django_allauth_steemconnect" to your INSTALLED_APPS setting like this::```pythonINSTALLED_APPS = [...'allauth','allauth.account','allauth.socialaccount','django_allauth_steemconnect.providers.steemconnect',]```2. Include the polls URLconf in your project urls.py like this::```pythonpath('accounts/', include('allauth.urls')),```3. Run `python manage.py migrate` to create the allauth models.4. Start the development server and visit http://127.0.0.1:8000/admin/to create a social app (you'll need the Admin app enabled).
Package: django-allauth-theme
django-allauth-themeAn awesome and responsive django-allauth theme based on tailwind.Installpipinstalldjango-allauth-themeConfiguring the settings fileFirst of all, addallauth_themeandcrispy_formstoINSTALLED_APPS.INSTALLED_APPS=(...'crispy_forms','allauth_theme',...)Add following context processors to the list:TEMPLATES=[{...'OPTIONS':{'context_processors':[...'allauth_theme.context_processors.welcome_text'],}}]Now include the urls in your urls.pyurlpatterns=[...path('',include('allauth_theme.urls')),...]Configuration for settings:DAT_WELCOME_TITLE='Welcome Title'# titleDAT_WELCOME_TITLE_MOBILE='Welcome mobile'# mobile titleDAT_WELCOME_TEXT='Description of your project'# text for your projectDAT_GOOGLE_ENABLE_ONETAP_LOGIN=True# decide if you want to show the google one tap loginDAT_GOOGLE_CLIENT_ID=''# google client id , e.g. XXXXXXXXXX39-62ckbbeXXXXXXXXXXXXXXXXXXXXXm1.apps.googleusercontent.comDAT_BASE_URL=''# e.g. http://localhost:8000Google One Tap LoginIf you want to use the google one tap you must you must include following changes to your settings for developement environment:Some notices for the developing environmentSECURE_REFERRER_POLICY='no-referrer-when-downgrade'Addhttp://localhost,http://localhost:8000,http://127.0.0.1andhttp://127.0.0.1:8000to your "Authorized JavaScript origins" in your google developer console. While you are working in the development environment you must use "localhost" instead of "127.0.0.1". As "Authorized redirect URIs" just use following URIs if you are working in the development environment:http://localhost:8000/accounts/google/login/callback/You can add also use 127.0.0.1 as URI if you don't want to use Google One Tap functionally while developing.