Clerk Handshake Cookie Not handeled?

[JoeAGarcia]

using gem 'clerk-sdk-ruby', '~> 4.0.0.beta4', require: 'clerk'

I noticed i had trouble signing out of my application only on a Production Env but in my Staging Env it works well. Both are Hosted obviously. The reason why i couldn't sign out was because Prod had a cookie named __Clerk_handshake on the client. Staging didn't have this cookie.
How do i know that this was my problem well i could successfully sign out when that cookie would expire or i would manually delete it .

This could be user error but I'm not sure

[tmilewski]

@JoeAGarcia Thanks for submitting this, but would you mind filing this over in clerk-sdk-ruby? This is a generated library specifically for the Backend API SDK methods.

[tmilewski]

@JoeAGarcia Transferred to clerk-sdk-ruby. Was this working in 4.0.0.beta3?

It's hard to tell from the screenshots but, at first glance, it would appear to me that the issue is the domain. What you'll notice is that the cookies are stored on the root .neighbors.solutions and, as a result, I think that you're seeing conflicts between your staging (admin-staging.neighbors.solutions) env and your production (admin.neighbors.solutions) env.

[jpowell]

@tmilewski can you help us figure out what our config should be? We've got the proper subdomain configured in the admin panel, but it appears the behavior is just different in prod vs development.

Would this config be on our server side? We're handling sessions and revoking on the server side, and using the react components to keep login on our domain on the client side.

Thoughts?

[tmilewski]

@jpowell Would you mind submitting a ticket here: https://clerk.com/contact/support. This will enable us to pull a lot more helpful information per your setup. Thanks!

[jpowell]

done