Bug 2030398 - Review Request: python-django-allauth - Integrated set of Django authentication apps
Summary: Review Request: python-django-allauth - Integrated set of Django authenticati...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: Package Review
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Neal Gompa
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: MailmanTracker 2030470
TreeView+ depends on / blocked
 
Reported: 2021-12-08 16:53 UTC by Michel Lind
Modified: 2021-12-17 01:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-12-17 01:11:31 UTC
Type: ---
Embargoed:
ngompa13: fedora-review+


Attachments (Terms of Use)

Description Michel Lind 2021-12-08 16:53:29 UTC
Spec URL: https://salimma.fedorapeople.org/specs/python/python-django-allauth.spec
SRPM URL: https://salimma.fedorapeople.org/specs/python/python-django-allauth-0.46.0-1.fc35.src.rpm
Description:
Integrated set of Django applications addressing authentication, registration,
account management as well as 3rd party (social) account authentication.

## Rationale
Most 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 your INSTALLED_APPS list.

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.

Fedora Account System Username: salimma

Koji scratch build: https://koji.fedoraproject.org/koji/taskinfo?taskID=79724113

Comment 1 Neal Gompa 2021-12-08 17:15:12 UTC
Review notes:

[x]: Package follows Fedora Python Packaging Guidelines
[x]: Package builds and installs
[x]: No serious issues from rpmlint
[x]: License is correctly identified and installed

PACKAGE APPROVED.

Comment 2 Michel Lind 2021-12-08 17:16:37 UTC
Thanks!

❯ fedpkg request-repo python-django-allauth 2030398
https://pagure.io/releng/fedora-scm-requests/issue/39122

Comment 3 Gwyn Ciesla 2021-12-08 18:36:33 UTC
(fedscm-admin):  The Pagure repository was created at https://src.fedoraproject.org/rpms/python-django-allauth

Comment 4 Fedora Update System 2021-12-15 19:19:38 UTC
FEDORA-2021-f19f2ab745 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-f19f2ab745

Comment 5 Fedora Update System 2021-12-16 02:08:32 UTC
FEDORA-2021-f19f2ab745 has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf install --enablerepo=updates-testing --advisory=FEDORA-2021-f19f2ab745 \*`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-f19f2ab745

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2021-12-17 01:11:31 UTC
FEDORA-2021-f19f2ab745 has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.