topic Re: Onboard Endpoint using API to then manage via MyDevice portal in Network Access Control

Onboard Endpoint using API to then manage via MyDevice portal

Tymofii Dmytrenko — Sun, 24 Mar 2019 18:56:35 GMT

Hello

We have created a simple website to onboard users' endpoints using just their MAC address, which we also assign to their AD username using portalUser attribute of Endpoint API. However, this is an interim tool... in future we would like to switch to Cisco ISE BYOD portals and we want all these MAC addresses that we add via API to then be visible under MyDevice portal (hence we create association of portalUser to MAC address).

I have noticed, that portal doesn't show these devices even though we are using the same format for portalUser as ISE (username@domain). We tried both methods - CREATE and REGISTER, but result is the same. The only difference is that REGISTER ignores Endpoint Group Id and puts endpoints into RegisteredDevices group regardless. It doesn't affect registration status, such as BYODRegistration, or DeviceRegistrationStatus, or IsRegistered endpoints' attributes

So, the question is simple. Is it possible to add endpoints into endpoints DB using API but also be able to manage them via MyDevices portal? What is the sequence (if possible at all)?

Thanks

Re: Onboard Endpoint using API to then manage via MyDevice portal

hslai — Mon, 25 Mar 2019 16:20:27 GMT

I am seeing the same in my lab so checking with our teams on this.

Re: Onboard Endpoint using API to then manage via MyDevice portal

Tymofii Dmytrenko — Sun, 07 Apr 2019 11:06:06 GMT

Thank you! Any update on this?

Would be great if there's a way to do it

We observe this behavior on ISE v2.3 Patch #5, but we are going to upgrade to ISE v2.4 latest patch in couple months. As long as it works in ISE v2.4 I will be happy 🙂

Re: Onboard Endpoint using API to then manage via MyDevice portal

Jason Kunst — Mon, 08 Apr 2019 23:19:28 GMT

this is still being researched

Re: Onboard Endpoint using API to then manage via MyDevice portal

Tymofii Dmytrenko — Tue, 09 Apr 2019 13:18:54 GMT

Thanks @Jason Kunst .

I am not sure why this one is marked as Solution Accepted though? Doesn't seem like there's a solution (yet)?

Re: Onboard Endpoint using API to then manage via MyDevice portal

Jason Kunst — Tue, 09 Apr 2019 13:52:33 GMT

This is being tracked internally as no one else in the public community can answer it then its not outstanding, we will follow up when we have the answer. It looks to be a long term fix that’s coming to track via a defect

Re: Onboard Endpoint using API to then manage via MyDevice portal

Tymofii Dmytrenko — Tue, 09 Apr 2019 15:49:09 GMT

Thanks. It does make sense.

May I also share the following observations with you?

Endpoint's 'name' field is quite useless when it comes to API. It is always set to MAC address ('mac' field), it can be set to anything when new endpoint is created (or existing one is edited), but this information is not shown anywhere (portals, Endpoint attributes, or even API itself - next time you query it will be set to mac address).

Would be very nice if this field actually represents the same thing as in portal as well - name of the device that end users set during onboarding.

Thanks a lot

Re: Onboard Endpoint using API to then manage via MyDevice portal

Jason Kunst — Tue, 11 Jun 2019 16:31:32 GMT

For anyone having issues like this it would be good to have a tac case and SR to track with defect as well