Skip to content
This repository has been archived by the owner on Oct 14, 2021. It is now read-only.

Invalidate caches when "Always require password at registration" changes #15

Open
mxr576 opened this issue Jul 9, 2019 · 2 comments
Open
Labels
bug Something isn't working

Comments

@mxr576
Copy link
Contributor

mxr576 commented Jul 9, 2019

If "user/register" form is in the render cache then changing "Always require password at registration" option does not add or remove the password field from the form.

@mxr576 mxr576 added the bug Something isn't working label Jul 9, 2019
@mxr576
Copy link
Contributor Author

mxr576 commented Jul 9, 2019

Cache tags/context on the user/register page.
image

@mxr576
Copy link
Contributor Author

mxr576 commented Jul 9, 2019

Also, if the above-mentioned option is enabled then when the authenticated user role's password policy changes then the user/register form's render array must be also removed from the page cache.

image

Maybe if this option is enabled then we should disable the page cache on the user/register completely? Or only the correct cache tags are missing from the policy config entity object? Like the entity ids of the roles, ex.: config:user.role.anonymous, config:user.role.authenticated.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant