-
Notifications
You must be signed in to change notification settings - Fork 27
Issues: w3c/webappsec-change-password-url
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Normative references to discontinued specs in A Well-Known URL for Changing Passwords
#42
opened Dec 6, 2023 by
dontcallmedom-bot
updated Dec 6, 2023
1 task
Be explicit that this specification is about "changing a password", not "resetting a password"
#39
opened May 4, 2022 by
danieljrmay
updated May 4, 2022
Any follow-up drafts for fully automated password change?
#34
opened May 12, 2021 by
dumblob
updated Feb 8, 2022
Clarify that redirects should be followed to resolve the Change Password URL
#15
opened Oct 18, 2019 by
rmondello
updated Nov 1, 2021
Update references & redirects to these documents
#31
opened Sep 23, 2020 by
hober
updated Sep 23, 2020
Specifying navigations affected by .well-known/change-password
#29
opened Sep 16, 2020 by
battre
updated Sep 16, 2020
response-code-reliability checking for OK Status
#24
opened Jun 15, 2020 by
battre
updated Jul 6, 2020
Broken reference for "Appropriate Use of Well-Known URIs"
#26
opened Jul 4, 2020 by
psimonyi
updated Jul 4, 2020
Add informative text clarifying that servers may use complex logic to determine where to redirect to
editorial
The requested change is non-normative
#4
opened Nov 14, 2018 by
craigfrancis
updated Oct 15, 2019
What should clients do on OK status?
clarification
Normative text is unclear
#7
opened Dec 8, 2018 by
jgimenez
updated Dec 12, 2018
Clarify interpretation of RFC5785 §1.1
clarification
Normative text is unclear
#9
opened Dec 11, 2018 by
hober
updated Dec 11, 2018
ProTip!
Updated in the last three days: updated:>2024-09-01.