config.cookie_enabled = true doesn't work?

[meliborn]

Based on https://devise-token-auth.gitbook.io/devise-token-auth/config/initialization I was trying to send auth toke via Cookie, but it doesn't work. Am I missed something?

[00dav00]

Hi @meliborn , do you have more details about the issue you are experiencing? Perhaps the backtrace of the error?

[mcelicalderon]

@meliborn @00dav00 I'm pretty sure the gem should be able to handle cookies correctly. We fixed this in the past #112 and I think it might be just a configuration problem, perhaps the base controller you are using. I need to do some testing, but if you could provide more details about how you are using this gem, that would help. Are you mounting in your own schema or using a separate route? Is your graphql controller api only?

[meliborn]

@it was mounted in the existing schema. Controller isn't an api only.

[00dav00]

@mcelicalderon The cookie referenced in #112 is the one set by Warden. The one DTA uses is this one which is set in an after action callback by DTA's SetUserByToken concern.

gql_devise concern SetUserByToken does not implement the callbacks that set this cookie, the only method wrapped from DTA is set_user_by_token which works to identify the user during the initial part the request.

I think this needs to be implemented. Could you confirm please?

[00dav00]

Hi @meliborn , the change on this PR implements the changes needed to set the auth cookies when you have this option configured in DTA.

It is important to consider that setting auth cookies will only work if you are using the schema in a GQL route within your main rails project. For now the route mounted using mount_graphql_devise_for is inhering from ActionController::API and can't be configured to inherit from a controller that includes the rails cookie concern.

This change is in master now and we will be releasing a new version of the next days.

[meliborn]

@00dav00 glad to hear!