Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API query for Engine Listing "Last Update" values #2

Closed
ghost opened this issue Oct 12, 2017 · 2 comments
Closed

API query for Engine Listing "Last Update" values #2

ghost opened this issue Oct 12, 2017 · 2 comments
Labels

Comments

@ghost
Copy link

ghost commented Oct 12, 2017

Anyone know where the "Last Update" values are extracted from in the Engine Listing? These are the Version, Content and Product values as seen in the Nexpose management dashboard. I can get the rest of the info via the API 'EngineListingRequest"..just these fields are proving elusive.

@gschneider-r7
Copy link
Contributor

Take a look at the Connection#engine_versions method. Under the hood it's sending an API request for ConsoleCommand with the command version engines and then parsing the plain-text response to capture key-value pairs. If you go to your console's administration page, then go to the "Run commands" link next to the "Troubleshooting" item (near the bottom right of the page) you can run the command version engines to see what the keys and values will look like - the ruby code just converts that to a hash.

There is an alternative method proposed which would parse the data from the UI endpoint instead, although it hasn't been accepted as a replacement (yet - I can't recall why). See rapid7/nexpose-client#231 for more info on that alternative.

@ghost
Copy link
Author

ghost commented Oct 23, 2017

Awesome. Cheers Gavin. Haven't had a chance to put it to the test yet, but now that I can see where it gets the data from I should be good to go.

@ghost ghost closed this as completed Oct 23, 2017
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant