sumith - hi team,while I'm currently posting ...
# dev-help
s
hi team, while I'm currently posting this payload: {"username":"UAT_6974","secret_key":"c6b21648-6c0a-4523-9ec1-19ec1367faac","org_id":"428140828"} to this endpoint:  https://terramar.thoughtspot.cloud/api/rest/2.0/auth/token/full I'm getting a 403 response. Any ideas?
j
hey @sumith , can u send the full error returned ? cc: @Swarnika @Piyush
s
@sumith any reason why you are still using that endpoint? can you please try api/rest/2.0/auth/token/custom?
s
Thank you for your message @User I have tried that other endpoint but am still getting the same 403 response. I am posting this payload: {"username":"UAT_6974","secret_key":"c6b21648-6c0a-4523-9ec1-19ec1367faac","org_id":"428140828"} to this endpoint: https://terramar.thoughtspot.cloud/api/rest/2.0/auth/token/custom ContentType and Accept properties on the request are both set to application/json Is it firstly worth checking that that payload should return a 200 response? As in, that the parameters are valid?
s
Can you please cross-check if your secret key is valid?
sample payload: curl -X POST \ --url 'https://champag*****-aws.thoughtspotstaging.cloud/api/rest/2.0/auth/token/custom' \ -H 'Accept: application/json' \ -H 'Content-Type: application/json' \ --data-raw '{ "username": "swarnika.gupta@thoughtspot.com", "validity_time_in_sec": 300, "persist_option": "REPLACE", "auto_create": true, "secret_key": "f8aa445b-5ff1-4a35-a58f-*********5" }'
s
yes its a valid secret key
s
Then, for troubleshooting it further, we need the HAR file and other logs.