Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(accounts): add key to password reset template #3108

Merged
merged 1 commit into from
Mar 30, 2023
Merged

feat(accounts): add key to password reset template #3108

merged 1 commit into from
Mar 30, 2023

Conversation

c-w
Copy link
Contributor

@c-w c-w commented Jun 3, 2022

Currently, the password reset email template gets passed the full URL to
the password reset endpoint. However, in some scenarios, this endpoint
isn't the location where the user will actually perform the password
reset data entry, for example if Django only hosts an API backend and
the user-facing part instead is implemented via a SPA.

To make it easier to integrate such setups with allauth, this change
additionally passes the uid and key to the password reset email
template. This provides full control to the template author to generate
their own password reset links and support a split frontend/backend.

Currently, the password reset email template gets passed the full URL to
the password reset endpoint. However, in some scenarios, this endpoint
isn't the location where the user will actually perform the password
reset data entry, for example if Django only hosts an API backend and
the user-facing part instead is implemented via a SPA.

To make it easier to integrate such setups with allauth, this change
additionally passes the uid and key to the password reset email
template. This provides full control to the template author to generate
their own password reset links and support a split frontend/backend.
@c-w
Copy link
Contributor Author

c-w commented Jun 3, 2022

Note the similar use-case in #3081; I believe the implementation provided here is more generic as the path variable can now be reconstructed in the template via reverse FYI @jhhayashi

@jhhayashi
Copy link

Makes sense to me. I'll close my PR in favor of this one

@c-w c-w closed this by deleting the head repository Dec 1, 2022
@c-w c-w reopened this Jan 16, 2023
@coveralls
Copy link

Coverage Status

Coverage: 91.689% (+0.4%) from 91.338% when pulling b45d5b3 on c-w:reset-password-uid-key into 1111078 on pennersr:master.

@c-w
Copy link
Contributor Author

c-w commented Mar 20, 2023

@pennersr Any chance we could get this PR reviewed? Thanks in advance!

@pennersr pennersr merged commit 0655cdf into pennersr:master Mar 30, 2023
@c-w
Copy link
Contributor Author

c-w commented Mar 30, 2023

TYSM for the merge!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants