Skip to content

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.

Sign up for GitHub

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

16 Open 14 Closed
16 Open 14 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Normative references to discontinued specs in A Well-Known URL for Changing Passwords
#42 opened Dec 6, 2023 by dontcallmedom-bot
1 task
Be explicit that this specification is about "changing a password", not "resetting a password"
#39 opened May 4, 2022 by danieljrmay
Any follow-up drafts for fully automated password change?
#34 opened May 12, 2021 by dumblob
6
Register with IANA
#32 opened Oct 7, 2020 by hober
@hober
Update references & redirects to these documents
#31 opened Sep 23, 2020 by hober
@hober
Specifying navigations affected by .well-known/change-password
#29 opened Sep 16, 2020 by battre
Broken reference for "Appropriate Use of Well-Known URIs"
#26 opened Jul 4, 2020 by psimonyi
response-code-reliability checking for OK Status
#24 opened Jun 15, 2020 by battre
@hober @rmondello
What about a link relation type?
#21 opened May 19, 2020 by dret
@rmondello
3
Malicious subdomain concern
#20 opened May 6, 2020 by hober
@rmondello
3
Expand security considerations section
#19 opened May 6, 2020 by hober
@hober
1
Who supports this?
#16 opened Dec 12, 2019 by marcoscaceres
@hober
9
Clarify that redirects should be followed to resolve the Change Password URL
#15 opened Oct 18, 2019 by rmondello
@hober
1
Clarify interpretation of RFC5785 §1.1 clarification Normative text is unclear
#9 opened Dec 11, 2018 by hober
@hober
What should clients do on OK status? clarification Normative text is unclear
#7 opened Dec 8, 2018 by jgimenez
@hober
1
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
@rmondello
4
ProTip! Add no:assignee to see everything that’s not assigned.