cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
831
Views
0
Helpful
1
Replies

Guest API Username Policy

daniegar
Level 1
Level 1

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">

    <customFields>

        <entry>

        </entry>

    </customFields>

    <guestAccessInfo>

        <fromDate>11/01/2016 10:43</fromDate>

        <location>San Jose</location>

        <toDate>11/01/2016 14:42</toDate>

        <validDays>1</validDays>

    </guestAccessInfo>

    <guestInfo>

        <enabled>true</enabled>

        <firstName>G****</firstName>

        <lastName>S****</lastName>

        <notificationLanguage>English</notificationLanguage>

    </guestInfo>

    <guestType>Daily (default)</guestType>

    <portalId>a0f9a290-e0e7-11e5-9151-005056bf7f51</portalId>

</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">

   <customFields>

     <entry>

       <key>ui_sponsorname_text_label</key>

       <value>J**** K*****</value>

     </entry>

   </customFields>

   <guestAccessInfo>

     <fromDate>10/31/2016 11:00</fromDate>

     <location>San Jose</location>

     <toDate>10/31/2016 18:00</toDate>

     <validDays>1</validDays>

   </guestAccessInfo>

   <guestInfo>

     <enabled>true</enabled>

     <notificationLanguage>English</notificationLanguage>

   </guestInfo>

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

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

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

1 Accepted Solution

Accepted Solutions

Jason Kunst
Cisco Employee
Cisco Employee

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?

View solution in original post

1 Reply 1

Jason Kunst
Cisco Employee
Cisco Employee

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?