I currently see no way with this module to access GET ${authUrl}/confirmation route in my backend, I can't imagine how I could verify user email addresses before letting them signin in my app.
I am using redux-token-auth for authentication with my backend Rails based with devise_token_auth
I expected that verifyToken and verifyCredentials to have different backend calls, respectively
verifyToken to GET ${authUrl}/confirmation, in order to validate the user email via the confirmation_token passed in the verification email
verifyCredentials to GET ${authUrl}/validate_token, in order to validate the user session via the token passed by the previous request (once the user is signed in)
Currently (in src/actions.ts) I see that verifyToken goes to GET ${authUrl}/validate_token, and verifyCredentials has an internal call to verifyToken, ending up to that same backend path
there's actually no need to deal with the verifyToken requests in the front end, I just set up my devise_token_auth to redirect back to my FE app, and it seems to work.
I currently see no way with this module to access
GET ${authUrl}/confirmation
route in my backend, I can't imagine how I could verify user email addresses before letting them signin in my app.I am using
redux-token-auth
for authentication with my backend Rails based withdevise_token_auth
I expected that
verifyToken
andverifyCredentials
to have different backend calls, respectivelyverifyToken
toGET ${authUrl}/confirmation
, in order to validate the user email via theconfirmation_token
passed in the verification emailverifyCredentials
toGET ${authUrl}/validate_token
, in order to validate the user session via thetoken
passed by the previous request (once the user is signed in)Currently (in
src/actions.ts
) I see thatverifyToken
goes toGET ${authUrl}/validate_token
, andverifyCredentials
has an internal call toverifyToken
, ending up to that same backend pathAny clues?