Service Mapping and Webseal

[haruesgap]

Hi All,

Looking for some wisdom since I'm stuck on a odd situation with Service Mapping and Webseal (hosted on ISAM). Overall situation is that while performing Top Down discovery, passed the LB level SM identifies connections to Webseal, and triggers horizontal discovery. However Discovery returns the next string:

https://<Webseal_Instance_IP >:443/api/v1/edge-clusters

<result error="Could not find any valid credentials to authenticate the target for type [BASIC_AUTH]"

The odd part is that we have SNMP credentials for ISAM enabled and Discovery can successfully retrieve the hierarchy and populate Webseal Table as well as as for Reverse Proxy, but Service Mapping is unable to go through Reverse Proxy which is on the CMDB.

Does anyone has seen this behavior?

[Brad Kallmeyer1]

WebSeal requires 2 sets of credentials, look at the error message it says your missing Basic Auth credentials.

https://docs.servicenow.com/bundle/xanadu-it-operations-management/page/product/service-mapping/refe...

[haruesgap]

Hey Brad,

Thanks for your reply. We have BASIC AUTH credentials. We found that at least for IBM ISAM Appliances once it got SNMP classified (during horizontal discovery) it never kicks-off HTTP Classify probes. (this one use Basic Auth Credentials) I had to create 2 behaviors for this, one that does just SNMP and after it immediately ends starts a HTTP one over the same devices.

We're able to see webseal instances created, however top down discovery is not finding the webseal based on the IP address

[pankajjajda]

Hi Hugo,

Let me know if you are able to get this map done.

We are also trying to map the same Webship application which uses webseal but not able to progress. 

Please reply.

Thanks.