We are delighted to share our new EIC Delivery Methodology for efficiently managing Saviynt Implementations and delivering quick time to value. CLICK HERE.

Error in getting Ticket Number. Response: null

Ash_saviynt1
New Contributor
New Contributor
When I try to set up create ticket with attestation revocation, I have configured both basic and oauth2 rest configurations, created a revocation task, and ran the Provisioning Job (WSRETRYJOB)task and it fails with the error 'Ticket Number. Response: null'
 
connection setting:
 
CreateTicketJSON:
{
"call": [{
"name": "call1",
"connection": "userAuth",
"httpMethod": "POST",
"httpParams": "{\"shortDescription\": \"saviyant testing new 20\",\"description\": \"Testingnew20\", \"application\": \"WMP\",\"userUID\": \"1006xxxx\"}",
"httpHeaders": {
"Authorization": "${accessToken}"},
"httpContentType": "application/json",
"successResponses": {
"statusCode": [
200,
201
]
}
}]
}
end pointsettings:  Service Desk Connection added connection details
 
 
error:
Error in getting Ticket Number. Response: null
 
Tried adding same json as
 
RemoveAccessJSON:
 
end pointsettings:  Provisioning Connection Connection added connection details
 
task completed no error message
 
As I tested in Postman, I received a 200 OK response status and no ticketid for basic authentication and ticket for outh2 rest call
 
Logs attached:
 
[This post has been edited by a Moderator to merge two posts.]
5 REPLIES 5

rushikeshvartak
All-Star
All-Star

ticketidPath Is missing in json

refer sample json https://docs.saviyntcloud.com/bundle/ServiceNow-v23x/page/Content/ServiceNow-as-a-Ticketing-System.h...


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

Yes, I tried the correct path and still got the same error.

 

postman response:

Ash_saviynt1_0-1702511995759.png

 

create ticket json

{
"call": [
{
"name": "call1",
"connection": "acctAuth",
"url": "https://servicedeskxxxxx",
"httpMethod": "POST",
"httpParams": "{\"shortDescription\": \"saviyant testing new 20\",\"description\": \"Testingnew20\", \"application\": \"WMP\",\"userUID\": \"1006xxxx\"}",
"httpHeaders": {
"Authorization": "Bearer eyJhbGciOiJodHRwOi8vd3d3LnczLm9yZy8yMDAxLzA0L3htbGRzaWctbW9yZSNobWFjLXNoYTI1NiIsInR5cCI6IkpXVCJ9.eyJodHRwOi8vc2NoZW1hcy54bWxzb2FwLm9yZy93cy8yMDA1LzA1L2lkZW50aXR5L2NsYWltcy9uYW1lIjoiYXBpX1Nhdml5bnQiLCJjbGllbnRfaWQiOiI5ZTJlYjdiOC0xOWMyLTRiM2ItOTYxMi02YzQyNDFkOTY0ZmUiLCJpZGVudCI6IntcImFwcGxpY2F0aW9uX3R5cGVcIjpcIkJyb3dzZXJDbGllbnRcIixcImF1dGhlbnRpY2F0aW9uX3R5cGVcIjpcIlRyZWJ1Y2hldFwiLFwidXNlcl9pZFwiOlwiYXBpX1Nhdml5bnRcIixcInNlY19ncnBcIjpcIjkzMzczNDAyZGE1OTYzNWJhOWU2MTY0Y2Y4OTM2NDc3NGEzYTJiZWJiMVwiLFwicGVyc29uYVwiOlwiOTM2NWE0NTJjNzBkNjlhNTcyNGJiMDQ2NTQ5ZTQ2NDg0ODNiODVmZGZjXCIsXCJ0b2tlblwiOm51bGwsXCJkZWZfdHlwZV9pZFwiOlwiOTMzODIxNmIzYzU0OWI3NTYwN2NmNTQ2NjdhNGU2N2QxZjY0NGQ5Zm"
},
"httpContentType": "application/json",
"ticketidPath": "busObPublicId",
"successResponses": {
"statusCode": [
200,
201
]
}
}
]
}

What is connection name both json i see different name 

is it userAuth /accAuth


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

@Ash_saviynt1 1.Please check the connection you have entered different name in CreateTicketJSON.

"connection": "acctAuth",

"connection": "userAuth",

 

2. 

"httpHeaders": {
"Authorization": "${access_token}"
},

 

Regards,
Sumathi Somala
If this reply answered your question, please Accept As Solution and give Kudos.

Rajesh-R
Saviynt Employee
Saviynt Employee

@Ash_saviynt1 - There seems to be a problem in your createTicketJSON:

This is the right usage: "Authorization": "${access_token}",

But looks like you are using  "Authorization": "${accessToken}" 

Please validate your JSON formation.


Thanks
Rajesh Ramalingam
Saviynt India