weird testing issue

[karmajunkie]

I'm using devise_rpx_connectable on a project, and I'm having a weird problem in testing. I'm using devise 1.1.3, devise_rpx_connectable 0.2.2.

Without :rpx_connectable on the model's devise strategies, everything works fine (i.e. using :database_authenticatable). once I integrate devise_rpx_connectable, however, the logged in user from rpx is not being remembered between redirects (i.e. user_signed_in? == false && current_user == nil)

I'm simulating the janrain engage service by skipping ahead to the callback and POSTing the token to my app, then mocking out the RPXNow.user_data call to return the appropriate identifier for the user. Stepping through it in the debugger it all works fine, until it gets to the redirect. Once I make it back into my controller through the redirect, warden isn't seeing the session user anymore.

I should note that it works fine in the development envronment. After it comes back from the engage server, it authenticates and the user_signed_in? and current_user helpers work as expected.

Am I missing something here? If there's a more appropriate forum please direct me to it.

[nicolasblanco]

Sorry, I don't have a clue.

As you can see I've written some basic test for the rpx strategy, just to ensure that there is no syntax error in it but that's all.