thank you @Alexis i understand and i appreciate your update :). having the toggle at both the collection and request action level is perfect. 
can’t wait to implement it.
Finally you will have it globally too, its in QA (testing) phase 
1 Like
awesome! @Alexis
@Alexis i see that the ‘Send credentials’ toggle has been live now, very exciting. I went ahead and implemented CORs settings on Xano + toggled on ‘Send credentials’ within WW.
While my requests are working, I’m not seeing the ‘cookie’ value getting set on Xano request.
For example, when ‘Send credentials’ is enabled on our GraphQL requests, I see two request cookies csrf_token and ory_kratos_session are being set. When the Xano request is being made, there are no Request cookies being included.
Can you please advise?
@Alexis i might have figured it out… it appears when our original cookie is set, the domain is not explicitly identified in the set_cookie details. provided we are making requests to the same url (which we are doing), the cookies will be included. however, since we’re now using a different subdomain, it appears we must indicate the domain with returned cookie to ensure it’s included in calls to the different subdomain. we will make this adjustment on our side and revert back with any findings.
1 Like
@Alexis confirmed all is working as expected now that we’ve updated our session cookie to properly indicate domain attribute when it’s first being set. nice job to you and the WW team getting this ‘send credentials’ functionality in place!
1 Like