Should I use the Devise Registrable module? (R: Yes!) about simple_token_authentication HOT 4 CLOSED

Hi @jamespeerless!

Exactly, it makes total sense to use the standard Devise registration mecanism. (That's simple separation of concerns, Simple Token Authentication does not aim at providing registration, thing that Devises does very well.)
As you correctly noted, the token authenticatable objects receive their authentication token via the ensure_authentication_token method and an Active Record callback.

In fact, the need to override the Devises::SessionsController is not related to token authentication by itself, but comes from the JSON requirement. It's only because that is a such common use case that I provided in #27 the SimpleToken Authentification-compatible SessionsController example you saw (and that I am using myself).

Go with Devise Registerable, that's the right way!

from simple_token_authentication.

Cool, thanks for the response. What if I also want the registration route to return a json representation of the user (or at the very least the authentication_token). I'm not using rails for any of the view layer, I use it only as a backend rest api for SPA's and mobile.

from simple_token_authentication.

In that case you should probably overwrite the Devise::RegistrationsController or part of it. There are several examples around the Devise documentation, I haven't any particular recommendation for that specific point but I'd love to hear which solution worked for you.

from simple_token_authentication.

@jamespeerless Here is an example of overriden Devise::RegistrationsController which may be interesting to you. ; )

from simple_token_authentication.