Service Mapping Credential issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-10-2016 08:37 AM
Hi Friends,
I'm trying my hands on service mapping and discovery. I have a set up as below.
Virtual box VM - Ubuntu 16 installed on it.
Apache
My SQL
Wordpress installed on this VM.
I saved the SSH credentials in the credential store and ran a normal discovery in IP range and application discovery. It ran fine and discovered the applications(Apache, My SQL). Even when i test the credentials from the credentials form it works fine.
When I try to run the service map on the wordpress installed with http as endpoint (http://IP/wordpress). It gives me below error in the service map.
Does any one encountered this error before?
- Labels:
-
Discovery
-
Service Mapping
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-11-2016 04:30 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-11-2016 08:52 AM
Hi Aniket,
Where do you have your credential store? Is it a store different than the one of your credentials section within the instance?
Thanks,
Berny
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-11-2016 08:57 AM
Hi Berny,
It's in the service now only. In the Service Map credential's.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-14-2016 04:12 AM
Hi Friends,
The issue seem to be instance specific. I used one of my friend's Geneva instance and it worked effortlessly. Thanks for your help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-23-2016 06:49 PM
We're facing the same issue, same error message referencing com.maverick.ssh. We ran packet captures with Wireshark from the MID server during flat discovery and again during service mapping discovery.
When running flat discovery, the client (MID server) is sending the SSH request using the SNC SSH client. When running service mapping discovery, it is using the legacy maverick client. When flat discovery runs, the SSH session gets set-up, the key exchange is successful, and it brings back data. When service mapping discovery runs, the SSH session dies after the server we're trying to discover returns undefined during the key exchange.
We've tried forcing the MID server to use the SNC SSH client, but no luck.
We have a HI ticket open, but was curious as to whether anyone has seen this before.
The boxes we're trying to discover are AIX servers and we're using Centrify SSH on them.