My goal is to create and invoke GitLab commands via ServiceNow Actions using a GitLab Spoke. I am attempting to setup my GitLab Spoke (Connect to a GitLab application) in ServiceNow using the instructions found at:
Google: “servicenow.com” "GitLab Spoke"
The error comes when I attempt to get the OAuth Token here:
…while logged into ServiceNow as admin, attempt to test it by copy-and-pasting the Token URL {Get OAuth Token} into the browser, I authorize ServiceNow application within GitLab:
…, then this is displayed:
Questions:
1. Is there any insight why this is not working or where I could find the correct Token URL?
2. It is plausible that this may arise with OAuth when the endpoints cannot communicate due to security/networks issues. However, both ServiceNow and GitLab are accessible on the same domain and not www publicly accessible. Are the Mid-servers adequate to authenticate OAuth 2.0?
3. The instructions explicitly state that the “Send Credentials” within the ServiceNow Application Registry should be set to <In Request Body (From URL-Encoded)>.
…If I change the “Send Credentials” to <As Basic Authentication Header>, would the change allow me to use the mid-server and the credentials for the GitLab spoke to connect to our GitLab instance while not compromising security?
4. What is the best means of testing the connectivity of the GitLab spoke to GitLab using an outbound RESTful Authentication action from ServiceNow?
