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: implement account recovery skeleton #428

Merged
merged 3 commits into from
Jun 5, 2020
Merged

Conversation

aeneasr
Copy link
Member

@aeneasr aeneasr commented May 19, 2020

See #37

To do:

  • Write tests for both recovery persisters
  • e2e tests

@aeneasr aeneasr marked this pull request as draft May 19, 2020 13:41
@aeneasr aeneasr mentioned this pull request Jun 3, 2020
2 tasks
@aeneasr aeneasr force-pushed the account-recovery branch 3 times, most recently from fac048e to e204a7b Compare June 3, 2020 15:13
@aeneasr aeneasr added this to the v0.4.0-alpha.1 milestone Jun 3, 2020
@aeneasr aeneasr added the feat New feature or request. label Jun 3, 2020
@aeneasr aeneasr self-assigned this Jun 3, 2020
@aeneasr aeneasr marked this pull request as ready for review June 3, 2020 15:17
@aeneasr aeneasr force-pushed the account-recovery branch from e204a7b to f494a83 Compare June 3, 2020 15:22
This patch implements the account recovery request skeleton with endpoints such as "Init Account Recovery", a new config value `urls�.recovery_ui` and so on.

Additionally, some refactoring was made to DRY code and make naming consistent.

See #37

BREAKING CHANGEs: The field `identity.addresses` has moved to `identity.verifiable_addresses`. A new field has been added
`identity.recovery_addresses`. Configuration key `selfservice.verify` was renamed to `selfservice.verification`. Configuration key `selfservice.verification.link_lifespan`
has been merged with  `selfservice.verification.request_lifespan`.
@aeneasr aeneasr force-pushed the account-recovery branch 4 times, most recently from cea5715 to fab48c9 Compare June 5, 2020 09:35
This patch implements the account recovery with endpoints such as "Init Account Recovery", a new config value `urls.recovery_ui` and so on. Additionally, some refactoring was made to DRY code and make naming consistent. As part of dependency upgrades, structured logging has also improved and an audit trail prototype has been added (currently streams to stderr only).

Closes #37

BREAKING CHANGES:

* Applying this patch requires running SQL Migrations.
* The field `identity.addresses` has moved to `identity.verifiable_addresses`. A new field has been added
`identity.recovery_addresses`. Configuration key `selfservice.verify` was renamed to `selfservice.verification`. Configuration key `selfservice.verification.link_lifespan`
has been merged with `selfservice.verification.request_lifespan`.
@aeneasr aeneasr force-pushed the account-recovery branch from fab48c9 to 63e404d Compare June 5, 2020 09:48
@aeneasr aeneasr merged commit e169a3e into master Jun 5, 2020
@aeneasr aeneasr deleted the account-recovery branch June 5, 2020 10:41
aeneasr added a commit to ory/kratos-selfservice-ui-node that referenced this pull request Jun 6, 2020
aeneasr added a commit to ory/kratos-selfservice-ui-node that referenced this pull request Jun 6, 2020
aeneasr added a commit that referenced this pull request Jun 6, 2020
This patch implements a better way to deal with text messages by giving them a unique ID, a context, and a default message.

Closes #428

BREAKING CHANGES: Flows, request methods, form fields have had a key errors to show e.g. validation errors such as ("not an email address", "incorrect username/password", and so on. The `errors` key is now called `messages`. Each message now has a `type` which can be `error` or `info`, an `id` which can be used to translate messages, a `text` (which was previously errors[*].message). This affects all login, request, settings, and recovery flows and methods.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feat New feature or request.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant