-
Notifications
You must be signed in to change notification settings - Fork 28
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
Request: add time-to-live option for /signin/generate-token
#731
Comments
Hey @hingobway, we're taking a look at this. |
@abergs & @hingobway The schema does mention https://v4.passwordless.dev/swagger/index.html It is marked as obsolete, but this is probably wrong, and I can see it being used in the back-end to return the authentication token. Likely was marked as obsolete as we wanted to prevent using it elsewhere in our own codebase. |
@jonashendrickx that's interesting, thanks. I actually didn't realize that that "Schema" switch in the docs was a button at all. Are you able to get that timeToLive parameter to work? I just tried including one, and it didn't seem to have any effect. |
@hingobway Does the following request work for you? You might have to change the
I just double checked locally everything was properly working. The If it is still not working, we can always verify in a call. |
Ok, it worked perfectly this time, not sure what I did last time. Sorry for the confusion, and thanks for your help! |
@hingobway You're welcome! In the next release, the property will show up properly in the Open API documentation. If you encounter any other issues, don't hesitate to reach out again! |
Docs fix: bitwarden/passwordless-docs#147 |
Hi,
I was implementing an alternative email provider for magic link sign-ins and got it working using the
/signin/generate-token
endpoint.However, as far as I can tell this endpoint has no configurable time-to-live, and only outputs tokens with a TTL of 2 minutes, which is far too short for email links. It would be great to make that option configurable!
The text was updated successfully, but these errors were encountered: