add get_endpoint_byname

[falkowich]

Tried to do this tonight..
Remembered that it isn't implemented yet.

Method:	GET
URI:	https://servername:9060/ers/config/endpoint/name/{name}

[E-ThanG]

I did a little tinkering with this a while ago. For some reason the name attribute worked oddly for me, maybe I should do more testing. IIRC get by name was fine, but the attribute wouldn't take assigned values and remained the same as the MAC address.

I added a function to get endpoints filtered by the portalUser attribute and use that instead. Maybe add that to the library too?

[falkowich]

I will check this out as soon as #164 is done

--
Falk

[falkowich]

Hi,

I added a function to get endpoints filtered by the portalUser attribute and use that instead. Maybe add that to the library too?

That seems like it would be a great addition, I would be really happy with a PR. Specially now when I have "chilled up with the changes" :)

--
Regads Falk

[E-ThanG]

I can do that. I have a TAC case open for the behavior of the portalUser attribute though, it seems to lose the value for reasons that I haven't yet determined. So its usefulness may be limited.

Regarding GET by name, I just tested (Correctly this time). That works fine.

However, if you wanted to modify that value you're out of luck. Attempting a PUT to the name attribute returns 200, but the value isn't actually updated.

https://{{ise_ers_api_host}}:9060/ers/config/endpoint/endpoint-id
Body:
'{ "ERSEndPoint": { "name": "name2" } }'

Response:
'{ "UpdatedFieldsList": { "updatedField": [] } }'

[E-ThanG]

Sorry for the long delay, do you still want a get by name function? The name IS the MAC address , so it may be a bit redundant .

Edit: Actually, it's a different API endpoint, the lookup would be done without the need of a filter

What branch should I use for PRs?