You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am having trouble obtaining and using the connect.sid cookie in Trudesk. Without this cookie, I am unable to access the API v2.
What I Have Tried:
I sent a request to POST /api/v2/login with valid credentials.
The response headers included a connect.sid cookie.
However, the connect.sid cookie appears to be invalid, as I still cannot authenticate and access API v2 using it. But, If I just copy and paste value of coonect.sid from the browser that logged into Trudesk, it works.
I also tried hitting the following endpoints, but none of them returned a valid connect.sid:
GET /api/v2/login
GET /api/v2/viewdata
Expected Behavior:
A valid connect.sid cookie should be returned upon successful login.
The cookie should allow authentication for API v2 requests.
Actual Behavior:
The connect.sid cookie retrieved from POST /login is invalid, preventing API access.
I would appreciate any guidance on why this is happening and how to obtain a working session cookie. Thanks!
The text was updated successfully, but these errors were encountered:
I am having trouble obtaining and using the
connect.sid
cookie in Trudesk. Without this cookie, I am unable to access the API v2.What I Have Tried:
POST /api/v2/login
with valid credentials.connect.sid
cookie.connect.sid
cookie appears to be invalid, as I still cannot authenticate and access API v2 using it. But, If I just copy and paste value of coonect.sid from the browser that logged into Trudesk, it works.connect.sid
:GET /api/v2/login
GET /api/v2/viewdata
Expected Behavior:
connect.sid
cookie should be returned upon successful login.Actual Behavior:
connect.sid
cookie retrieved fromPOST /login
is invalid, preventing API access.I would appreciate any guidance on why this is happening and how to obtain a working session cookie. Thanks!
The text was updated successfully, but these errors were encountered: