You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just after setting a new password following the recovery password/settings flow, a verification email (like the one sent after user registration) is sent to the user.
Reproducing the bug
Steps to reproduce the behavior:
With a user registered (verification via email enabled and a verification email should be sent (I'm using MailSlurper))...
A recovery email should be received with a link and token. Follow this link and get the response cookies (ory_kratos_session and csrf_token) and the new <request> code.
Get settings request context (I'm using admin port because I'm doing it from a backend): curl 'http://127.0.0.1:4434/self-service/browser/flows/requests/settings?request=<request>' --header 'Cookie: ory_kratos_session=<csrf_token_cookie>'
Get <csrf_token_form_value> from response body (methods.password.config.fields -> csrf_token value)
Complete the settings flow for the password strategy: curl --location --request POST 'http://127.0.0.1:4433/self-service/browser/flows/settings/strategies/password?request=<request>' --header 'Cookie: csrf_token<csrf_token_cookie>' --form 'password=<new_password>' \ --form 'csrf_token=<csrf_token_form_value>'
At this point, the password has changed and I receive a verification email.
Describe the bug
Just after setting a new password following the recovery password/settings flow, a verification email (like the one sent after user registration) is sent to the user.
Reproducing the bug
Steps to reproduce the behavior:
With a user registered (verification via email enabled and a verification email should be sent (I'm using MailSlurper))...
curl 'http://127.0.0.1:4433/self-service/browser/flows/recovery'
<request>
code and<csrf_token_cookie>
.curl 'http://127.0.0.1:4433/self-service/browser/flows/requests/recovery?request=<request>' --header 'Cookie: csrf_token=<csrf_token_cookie>'
<csrf_token_form_value>
from response body (methods.link.config.fields -> csrf_token value
)curl --request POST 'http://127.0.0.1:4433/self-service/browser/flows/recovery/link?request=<request>' --header 'Cookie: csrf_token=<csrf_token_cookie>' --header 'Content-Type: application/x-www-form-urlencoded' --data-urlencode 'csrf_token=<csrf_token_form_value>' --data-urlencode 'email=<email>'
ory_kratos_session
andcsrf_token
) and the new<request>
code.curl 'http://127.0.0.1:4434/self-service/browser/flows/requests/settings?request=<request>' --header 'Cookie: ory_kratos_session=<csrf_token_cookie>'
<csrf_token_form_value>
from response body (methods.password.config.fields -> csrf_token value
)curl --location --request POST 'http://127.0.0.1:4433/self-service/browser/flows/settings/strategies/password?request=<request>' --header 'Cookie: csrf_token<csrf_token_cookie>' --form 'password=<new_password>' \ --form 'csrf_token=<csrf_token_form_value>'
Server configuration
config.yaml
User schema:
Expected behavior
The verification email shouldn't be sent at the end of the recovery process.
Environment
The text was updated successfully, but these errors were encountered: