yortz
commented
1 year ago I tried with version 1.2.1 and the result remains the same, this is really weird since the callback is successfully returning the auth hash, I even got the code passed as param to the callback and this sets the session, the user is successfully signed in, all auth params are in place, I even tried to add back sprockets since I noticed this has been removed thinking this was the cause of the issue, but no way to get past this weird behaviour. The strange thing is that if I add an override for the external omniauth page, or if I directly try to edit the one for the gem (by mounting devise_token_auth in my Gemfile to use the local version I cloned on my machine), no updates are reflected in the page, so let is say that for example I am doing something like this in my custom override
#app/views/devise_token_auth/omniauth_external_window.html.erb
<!DOCTYPE html>
<html>
<head>
</head>
<body>
<p>Hello World</p>
</body>
</html>Instead of seeing at least the text comment in the template, it literally always renders an empty view, this is totally weird, in this way I am prevented to have the @data passed into the view and then do the redirect to my FE app, by the way no sort of js is triggered in this page if I include any inside of a <script> tag I am totally stuck on this...
Hi, first of all, let me say that I have been using devise token auth since 2017 and I have integrated various types of authentications (with regular username and pwd) and other custom omniauth strategies with success. I have been using this library to authenticate with various web client apps (ember, react) flawlessly. Now after all these years, I decided to update the version of devise token auth from
1.1.0to1.2.0. I am onrails 6.1.7.1.I have been running the current specs for my code base and out of 509 examples, it seems that I have only 1 spec failing; by having a look at what is going on, it seems that for some unknown reason, the spec is failing since the
response.bodyfor the callback response is an empty string and the@datacoming from therender_data(message, data)method in theomniauth_callbacks_controller.rbis not passed to theomniauth_external_window.html.erbview (as instead it was happening with version1.1.0). This is totally weird, since if I directly debug from insidedevise_token_authand I inspect what is going on in therender_data(message, data)method my@datais there, here is an example of calling@data.to_jsonfrom the methodbut to my great surprise, it seems that when I am redirected to
auth/provider/callbackpage, this page is always empty, no js is executed (I tried to put aconsole.login there to see if I could debug something from the view), I even tried to manually place some plain text in the body to understand if I could at least have the@dataincluded in this page by using simple ERB but no matter what, this is always rendering an empty page: the@datais not passed to the view and the sign in is successfull, since if I inspect the current user, this user is signed in and authenticated to the rails app (the sign in count is updated in my db table) but the@datais not passed anymore in the view with version1.2.0as it was happening with version1.1.0and no js is executed, I am totally stuck on this and I do not understand if this has anything to do with the new changes in the version1.2.0or if this has something to do with the version of rails, has anyone by chance experienced this same type of issue with version1.2.0of devise token auth? Any kind of support on this would be highly appreciated, thanks in advance!