Getting An error - AWS connect - Voice agent
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
HI All -
I trying to connect AWS connect for my voice agent as communication channels. As per the guide , i see we need to share these three information to AWS side to be configured.
while i got other information, i got stuck here up on these one information,
1. ssm_oauth_path, as it is given " The base path for OAuth credentials in AWS Parameter Store: /com.servicenow.cti/<sn-instance-id>/<voice-service-id>. Set after completing the Parameter Store setup in the following steps "
now , what is this <voice-service-id>,to be taken.
do i need to take the sys_id from the url ? if so, i am getting this error below,
{ "level": "ERROR", "message": "Failed to obtain access token", "error": "OAuth token request failed: HTTP 401 for POST tataamericaintlcorpdemo2.service-now.com/oauth_token.do"}
any help will be appreciated .
PaulSylo
To be is to do. To do is to be.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @Paulsylo,
That access_denied/server_error pair is coming out of your own instance's oauth_token.do, not AWS. On a Client Credentials grant, ServiceNow throws this exact combo when it can't resolve a valid identity behind the token request, and in practice that's almost always the OAuth Application User on the Application Registry record, not the secret you already fixed.
- Confirm the OAuth Application User field on the registry is populated and points to an active, unlocked user
- Make sure that user has the roles your Voice/Connect integration actually needs, since the token inherits its access from this user's roles
- Verify the system property glide.oauth.inbound.client.credential.grant_type.enabled is true
- Check the registry's Default Grant Type is actually set to Client Credentials, not just listed as an available grant
Thank you,
Vikram Karety
Octigo Solutions INC
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @Paulsylo
Share your oauth profile screen shot
Try once with grant type as Client credential if you are using grant type : Authorization code
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago