topic Re: com.cisco.endpoint.asset service is not queryable via API in Network Access Control

com.cisco.endpoint.asset service is not queryable via API

JustinLute — Tue, 11 Jun 2019 14:23:07 GMT

My ultimate goals are to be able to execute the getAssets API query to be able to see all of the existing endpoints. Then to selectively CREATE, UPDATE, and DELETE endpoint records.

I'm viewing this document. Page 126 indicates that the base URL is https://[ind-host1]:8910/pxgrid/ind/asset. This does not seem to work for me.

Page 127 instead says that I need to execute a ServiceLookup against com.cisco.endpoint.asset. This query returns no results for me. The com.cisco.endpoint.asset topic does appear to be running/listing when I look at the pxGrid section of the ISE UI.

What might I be missing?

Re: com.cisco.endpoint.asset service is not queryable via API

Jason Kunst — Tue, 11 Jun 2019 15:40:38 GMT

Is there a reason using the pxgrid API and not the regular http://cs.co/ise-api

Re: com.cisco.endpoint.asset service is not queryable via API

JustinLute — Tue, 11 Jun 2019 16:21:54 GMT

Yes, I'm focusing on pxGrid because all of the documentation I am reading points me down this path. pxGrid is the "new" API. It has functionality specifically for IoT Context-In, which is my initial use case.

Re: com.cisco.endpoint.asset service is not queryable via API

jeppich — Tue, 11 Jun 2019 16:42:46 GMT

Hey Justin,

This code references the pxGrid context-in code, in which you have a pxGrid client publishing asset information into pxGrid over the endpoint asset Topic.

For more information please see: https://developer.cisco.com/docs/pxgrid/#!pxgrid-context-in

If you have any questions, please email me directly.

Thanks,

John

jeppich@cisco.com

Re: com.cisco.endpoint.asset service is not queryable via API

Jason Kunst — Tue, 11 Jun 2019 16:57:38 GMT

pxGRID API is for those items. Its not new, it has been around for a long time. The other APIs (including guest) have other purposes. Context-in is for sending items into ISE. This is part of the devnet community for integrating with partners as john mentioned. If you have use cases for that then work with him.