- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-10-2020 07:58 AM
We have a azure Integration setup to enable and disable the user in azure from servicenow
We are using OOB spokes , we are facing a strange error. not sure what is the issue.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-21-2020 02:38 PM
The most common reason is that the Connection URL in your "HTTP(s) Connection" doesn't have the correct protocol defined. There must (typically) be a http:// or https:// in front of the target to work properly.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-21-2020 02:38 PM
The most common reason is that the Connection URL in your "HTTP(s) Connection" doesn't have the correct protocol defined. There must (typically) be a http:// or https:// in front of the target to work properly.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-07-2021 11:13 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-07-2021 11:53 AM
You want to ensure the 'HTTP(s) Connection' record for the 'sn_azure_ad_spoke.AzureAD' Connection & Credential Alias is fully qualified. The "Connection URL" field must start with "https://" (the active item on the "Connections" tab).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-23-2023 11:49 AM
This was my issue. A missing protocol in the connection record for the connection url field. thanks for the fix! Odd that it was working for some REST actions and not others...