Forum Discussion
NimbostratusServiceNow discovery and service mapping
Our organization is switching to ServiceNow, as part of the implementation of it the project team wants to be able to discover the F5 BIG-IPs and service mappings. We were able to get the devices discovered after some trial and error with the device certificates. We are now getting stuck on service mapping portion. My understanding is that they are using F5 Rest pattern. Documentation that we were provided is the following:
When they try to perform the service mapping discovery portion they get a 401 authentication error on the SNOW discovery tool. We are running BIG-IP 17.1.3.4. Curious if anyone has struggled with the Service mapping portion and if so if you can share your experience/workarounds so we can at least get going in the right direction.
1 Reply
- Aswin_mk
MVP
Hello,
F5 introduced additional security controls for REST tokens in newer releases. One common issue is that a token becomes tied to the client IP that created it. If a token is generated from one source and reused from another, BIG-IP can return 401 Unauthorized. I've seen integrations break after upgrades because of this behavior change. If ServiceNow/MID is tokenizing credentials and then reusing tokens unexpectedly, this is worth investigating in the BIG-IP logs.
Useful logs:
Shell
1
/var/log/restjavad.*
2
/var/log/httpd/httpd_errors
Show more lines
Look for authentication failures or token client mismatch messages, if all ok try to restart below services .
bigstart status restjavad
bigstart status restnoded
Also please add service now IPs in httpd allow, if you have any blocking in management IP.
