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
Now outlook will wrap any url with safelinks, which upon click will access the link on behalf of the user first before redirecting the user.
I implemented the handover of jwt at server side rendering setting httpOnly cookie.
I think could wrap another redirect at browser side which then actually calls the login API. Or, can we have a switch to allow re-use of the link or only invalidate the link after few access counts instead of 1.
Now outlook will wrap any url with safelinks, which upon click will access the link on behalf of the user first before redirecting the user.
I implemented the handover of jwt at server side rendering setting httpOnly cookie.
I think could wrap another redirect at browser side which then actually calls the login API. Or, can we have a switch to allow re-use of the link or only invalidate the link after few access counts instead of 1.
Seems Related:
#16
The text was updated successfully, but these errors were encountered: