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

Enforce password reset #35

Closed
aeneasr opened this issue Jul 22, 2019 · 6 comments
Closed

Enforce password reset #35

aeneasr opened this issue Jul 22, 2019 · 6 comments
Labels
package/selfservice Affects selfservice components
Milestone

Comments

@aeneasr
Copy link
Member

aeneasr commented Jul 22, 2019

In some cases, we might want to (enforce) password reset:

@aeneasr aeneasr added the package/selfservice Affects selfservice components label Jul 22, 2019
@aeneasr aeneasr added this to the v0.0.2 milestone Jul 22, 2019
@stale stale bot added the stale label Jul 23, 2019
@aeneasr aeneasr removed the stale label Jul 23, 2019
@ory ory deleted a comment from stale bot Jul 23, 2019
@aeneasr aeneasr modified the milestones: v0.4.0-alpha.1, v0.6.0-alpha.1 Jun 8, 2020
@aeneasr
Copy link
Member Author

aeneasr commented Jun 8, 2020

It's better to solve this using account recovery I believe�. Still needs to be documented.

@zhengm-hub
Copy link

When will it be supported

@aeneasr

@aeneasr
Copy link
Member Author

aeneasr commented Mar 15, 2021

While I understand that a date of delivery is helpful when planning, we stopped giving out due dates for features or milestones. It puts maintainers in an unfair spot as

  1. there are many things going on in the community which need time (reviewing PRs, addressing issues, answering questions) and demand is no not easily foreseeable;
  2. maintainers do a lot of things in their free time and can not commit to deliver something;
  3. internal priorization can shift at any point in time

When we do give out due dates, we often encounter people who are pissed off because something was promised and not delivered "on time" (as free software ;) ). Unfortunately that is the sad truth of many interactions in this context which is why we stopped doing it altogether.

Having said that, you are in the privileged position of being part in a global open source community! If you think that you can contribute towards the particular feature, maintainers will do their best to give you the right pointers and review PRs.

If that's not an option, you can consider to become a Ory Sponsor on Open Collective or Patreon. This helps us to employ more maintainers and technical staff - increasing velocity in development, community, interaction, and other areas! All collected money goes directly into this.

@sebmellen
Copy link

Is this issue still being tracked, or is there some workaround? Loving Ory so far, this would be an important feature!

@aeneasr
Copy link
Member Author

aeneasr commented Mar 23, 2022

You can now set the password of a user to something random using the identity admin API, and then send them a recovery link through the API :)

@aeneasr
Copy link
Member Author

aeneasr commented Mar 13, 2023

No upvotes, noone really interested in this feature. Closing.

@aeneasr aeneasr closed this as not planned Won't fix, can't repro, duplicate, stale Mar 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
package/selfservice Affects selfservice components
Projects
None yet
Development

No branches or pull requests

3 participants