Guest API Username Policy

daniegar — Tue, 01 Nov 2016 22:10:31 GMT

I'm helping a customer with the Guest API and I see two different behaviors on username selection policy that I cannot understand how to configure.

Using the POST method to generate a new Guest user, the username I got from ISE was derived from First and Last Name, but the customer's was completely random ("e1~06h2ol").

We have both default Guest Username Policies. I'd like to understand how to determine and configure the username policy for Guest creation using the API.

My request

curl -X POST -H "Authorization: Basic *************************" -H "Content-Type: application/vnd.com.cisco.ise.identity.guestuser.2.0+xml" -H "Accept: application/vnd.com.cisco.ise.identity.guestuser.2.0+xml" -d '<?xml version="1.0" encoding="utf-8" standalone="yes"?>

<ns4:guestuser xmlns:ers="ers.ise.cisco.com" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ns4="identity.ers.ise.cisco.com">

<entry>

</entry>

</customFields>

</guestAccessInfo>

<notificationLanguage>English</notificationLanguage>

</guestInfo>

<guestType>Daily (default)</guestType>

</ns4:guestuser>' "https://10.0.0.131:9060/ers/config/guestuser"

Customer's request

curl -v -u ********:******* -H "Content-Type: application/vnd.com.cisco.ise.identity.guestuser.2.0+xml" -H "Accept: application/vnd.com.cisco.ise.identity.guestuser.2.0+xml" -X POST -d '<?xml version="1.0" encoding="utf-8" standalone="yes"?>

<ns4:guestuser xmlns:ers="ers.ise.cisco.com" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ns4="identity.ers.ise.cisco.com">

<entry>

<key>ui_sponsorname_text_label</key>

</entry>

</customFields>

</guestAccessInfo>

<notificationLanguage>English</notificationLanguage>

</guestInfo>

<guestType>****Guest</guestType>

<portalId>d0e59882-acc5-11e4-ae1b-000c292eb2a5</portalId>'

</ns4:guestuser>' "https://ise***.******.com:9060/ers/config/guestuser"

Re: Guest API Username Policy

Jason Kunst — Thu, 03 Nov 2016 18:58:55 GMT

Sorry I was incorrect, the API should use the same policy, only if the first/last or email address is missing then it would create it randomly. What release is the customer on?

topic Guest API Username Policy in Network Access Control

Guest API Username Policy

Re: Guest API Username Policy