<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic ISE 2.4 API header to send email to guests in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-2-4-api-header-to-send-email-to-guests/m-p/3755960#M543529</link>
    <description>&lt;P&gt;I am running ISE 2.4.0.357 and the function to send e-mail to guests by using API calls is not working.&lt;BR /&gt;I guess that the documention is informing the wrong headers for this call.&lt;BR /&gt;This is what I see in the live documentation (&lt;A href="https://1.1.1.1:9060/ers/sdk#email" target="_blank"&gt;https://1.1.1.1:9060/ers/sdk#email&lt;/A&gt;&lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;BR /&gt;Method: PUT&lt;BR /&gt;URI: &lt;A href="https://1.1.1.1:9060/ers/config/guestuser/email/{id}/portalId/{portalId" target="_blank"&gt;https://1.1.1.1:9060/ers/config/guestuser/email/{id}/portalId/{portalId&lt;/A&gt;}&lt;BR /&gt;HTTP 'Content-Type' Header: application/xml | application/json&lt;BR /&gt;HTTP 'Accept' Header: application/xml | application/json&lt;BR /&gt;HTTP 'ERS-Media-Type' Header (Not Mandatory): identity.guestuser.2.0&lt;BR /&gt;HTTP 'X-CSRF-TOKEN' Header (Required Only if Enabled from GUI): The Token value from the GET X-CSRF-TOKEN fetch request&lt;BR /&gt;Bulk Support: Operation 'email' can be used within Bulk Request.&lt;BR /&gt;Additional Attributes: senderEmail&lt;BR /&gt;Request Content:&lt;BR /&gt;XML&lt;BR /&gt;&amp;lt;?xml version="1.0" encoding="UTF-8"?&amp;gt;&lt;BR /&gt;&amp;lt;ns0:operationAdditionalData xmlns:ns0="ers.ise.cisco.com" xmlns:xs="&lt;A href="http://www.w3.org/2001/XMLSchema" target="_blank"&gt;http://www.w3.org/2001/XMLSchema&lt;/A&gt;"&amp;gt;&lt;BR /&gt; &amp;lt;requestAdditionalAttributes&amp;gt;&lt;BR /&gt; &amp;lt;additionalAttribute name="senderEmail" value="value_0"/&amp;gt;&lt;BR /&gt; &amp;lt;/requestAdditionalAttributes&amp;gt;&lt;BR /&gt;&amp;lt;/ns0:operationAdditionalData&amp;gt;&lt;BR /&gt;JSON&lt;BR /&gt;{&lt;BR /&gt; "OperationAdditionalData" : {&lt;BR /&gt; "additionalData" : [ {&lt;BR /&gt; "name" : "example additional attribute name",&lt;BR /&gt; "value" : "its value"&lt;BR /&gt; } ]&lt;BR /&gt; }&lt;BR /&gt;}&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;I performed many tests. By using JSON and XML and it didn’t work.&lt;/P&gt;
&lt;P&gt;Do you guys know what is the correct header?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Example tests:&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Header "Content-Type: application/xml"&lt;/STRONG&gt;&lt;BR /&gt;[user@server]$ cat xml.xml&lt;BR /&gt;&amp;lt;?xml version="1.0" encoding="UTF-8"?&amp;gt;&lt;BR /&gt;&amp;lt;ns0:operationAdditionalData xmlns:ns0="ers.ise.cisco.com" xmlns:xs="&lt;A href="http://www.w3.org/2001/XMLSchema" target="_blank"&gt;http://www.w3.org/2001/XMLSchema&lt;/A&gt;"&amp;gt;&lt;BR /&gt; &amp;lt;requestAdditionalAttributes&amp;gt;&lt;BR /&gt; &amp;lt;additionalAttribute name="senderEmail" value="email@example.com"/&amp;gt;&lt;BR /&gt; &amp;lt;/requestAdditionalAttributes&amp;gt;&lt;BR /&gt;&amp;lt;/ns0:operationAdditionalData&amp;gt;&lt;BR /&gt;[user@server]$ curl --tlsv1.1 -v -k -X 'PUT' -H "Content-Type: application/xml" -d @xml.xml 'https://sponsor:XXX@1.1.1.1:9060/ers/config/guestuser/email/31e8ca71-f49e-11e8-bc83-2e9d9d140649/portalId/36a96010-c267-11e8-89ad-2e2e02dc7046'&lt;/P&gt;
&lt;P&gt;ERROR: &amp;lt; HTTP/1.1 415 Unsupported Media Type&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Header "Content-Type: application/json"&lt;/STRONG&gt;&lt;BR /&gt;[user@server]$ curl --tlsv1.1 -v -k -X 'PUT' -H 'Content-Type: application/json' -d '{"OperationAdditionalData":{"additionalData":[{"name":"senderEmail","value":"email@example.com"}]}}' 'https://sponsor:XXX@1.1.1.1:9060/ers/config/guestuser/email/31e8ca71-f49e-11e8-bc83-2e9d9d140649/portalId/36a96010-c267-11e8-89ad-2e2e02dc7046'&lt;BR /&gt;ERROR: &amp;lt; HTTP/1.1 415 Unsupported Media Type&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Header "Content-Type: application/json" “ACCEPT: application/json”&lt;/STRONG&gt;&lt;BR /&gt;[user@server]$ curl --tlsv1.1 -v -k -X 'PUT' -H 'ACCEPT: application/json' -H 'Content-Type: application/json' -d '{"OperationAdditionalData":{"additionalData":[{"name":"senderEmail","value":"email@example.com"}]}}' 'https://sponsor:XXX@1.1.1.1:9060/ers/config/guestuser/email/31e8ca71-f49e-11e8-bc83-2e9d9d140649/portalId/36a96010-c267-11e8-89ad-2e2e02dc7046' &lt;BR /&gt;ERROR: &amp;lt; HTTP/1.1 500 Internal Server Error&lt;BR /&gt;&amp;lt; Server:&lt;BR /&gt;&amp;lt;&lt;BR /&gt;{&lt;BR /&gt; "ERSResponse" : {&lt;BR /&gt; "operation" : "PUT-email-guestuser",&lt;BR /&gt; "messages" : [ {&lt;BR /&gt; "title" : "Email request for GuestUser with ID (31e8ca71-f49e-11e8-bc83-2e9d9d140649) failed due to Error while generating Email ",&lt;BR /&gt; "type" : "ERROR",&lt;BR /&gt; "code" : "CRUD operation exception"&lt;BR /&gt; } ],&lt;BR /&gt; "link" : {&lt;BR /&gt; "rel" : "related",&lt;BR /&gt; "href" : "&lt;A href="https://1.1.1.1:9060/ers/config/guestuser/email/31e8ca71-f49e-11e8-bc83-2e9d9d140649/portalId/36a96010-c267-11e8-89ad-2e2e02dc7046" target="_blank"&gt;https://1.1.1.1:9060/ers/config/guestuser/email/31e8ca71-f49e-11e8-bc83-2e9d9d140649/portalId/36a96010-c267-11e8-89ad-2e2e02dc7046&lt;/A&gt;",&lt;BR /&gt; "type" : "application/xml"&lt;BR /&gt; }&lt;BR /&gt; }&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;HEADER "Content-Type: application/vnd.com.cisco.ise.identity.guestuser.2.0+xml"&lt;/STRONG&gt;&lt;BR /&gt;[user@server]$ curl --tlsv1.1 -v -k -X 'PUT' -H "Content-Type: application/vnd.com.cisco.ise.identity.guestuser.2.0+xml" -d @xml.xml 'https://sponsor:XXX@1.1.1.1:9060/ers/config/guestuser/email/31e8ca71-f49e-11e8-bc83-2e9d9d140649/portalId/36a96010-c267-11e8-89ad-2e2e02dc7046'&lt;BR /&gt;ERROR: &amp;lt; HTTP/1.1 415 Unsupported Media Type&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 08:52:36 GMT</pubDate>
    <dc:creator>thiagosilvino</dc:creator>
    <dc:date>2019-03-11T08:52:36Z</dc:date>
    <item>
      <title>ISE 2.4 API header to send email to guests</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-api-header-to-send-email-to-guests/m-p/3755960#M543529</link>
      <description>&lt;P&gt;I am running ISE 2.4.0.357 and the function to send e-mail to guests by using API calls is not working.&lt;BR /&gt;I guess that the documention is informing the wrong headers for this call.&lt;BR /&gt;This is what I see in the live documentation (&lt;A href="https://1.1.1.1:9060/ers/sdk#email" target="_blank"&gt;https://1.1.1.1:9060/ers/sdk#email&lt;/A&gt;&lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;BR /&gt;Method: PUT&lt;BR /&gt;URI: &lt;A href="https://1.1.1.1:9060/ers/config/guestuser/email/{id}/portalId/{portalId" target="_blank"&gt;https://1.1.1.1:9060/ers/config/guestuser/email/{id}/portalId/{portalId&lt;/A&gt;}&lt;BR /&gt;HTTP 'Content-Type' Header: application/xml | application/json&lt;BR /&gt;HTTP 'Accept' Header: application/xml | application/json&lt;BR /&gt;HTTP 'ERS-Media-Type' Header (Not Mandatory): identity.guestuser.2.0&lt;BR /&gt;HTTP 'X-CSRF-TOKEN' Header (Required Only if Enabled from GUI): The Token value from the GET X-CSRF-TOKEN fetch request&lt;BR /&gt;Bulk Support: Operation 'email' can be used within Bulk Request.&lt;BR /&gt;Additional Attributes: senderEmail&lt;BR /&gt;Request Content:&lt;BR /&gt;XML&lt;BR /&gt;&amp;lt;?xml version="1.0" encoding="UTF-8"?&amp;gt;&lt;BR /&gt;&amp;lt;ns0:operationAdditionalData xmlns:ns0="ers.ise.cisco.com" xmlns:xs="&lt;A href="http://www.w3.org/2001/XMLSchema" target="_blank"&gt;http://www.w3.org/2001/XMLSchema&lt;/A&gt;"&amp;gt;&lt;BR /&gt; &amp;lt;requestAdditionalAttributes&amp;gt;&lt;BR /&gt; &amp;lt;additionalAttribute name="senderEmail" value="value_0"/&amp;gt;&lt;BR /&gt; &amp;lt;/requestAdditionalAttributes&amp;gt;&lt;BR /&gt;&amp;lt;/ns0:operationAdditionalData&amp;gt;&lt;BR /&gt;JSON&lt;BR /&gt;{&lt;BR /&gt; "OperationAdditionalData" : {&lt;BR /&gt; "additionalData" : [ {&lt;BR /&gt; "name" : "example additional attribute name",&lt;BR /&gt; "value" : "its value"&lt;BR /&gt; } ]&lt;BR /&gt; }&lt;BR /&gt;}&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;I performed many tests. By using JSON and XML and it didn’t work.&lt;/P&gt;
&lt;P&gt;Do you guys know what is the correct header?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Example tests:&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Header "Content-Type: application/xml"&lt;/STRONG&gt;&lt;BR /&gt;[user@server]$ cat xml.xml&lt;BR /&gt;&amp;lt;?xml version="1.0" encoding="UTF-8"?&amp;gt;&lt;BR /&gt;&amp;lt;ns0:operationAdditionalData xmlns:ns0="ers.ise.cisco.com" xmlns:xs="&lt;A href="http://www.w3.org/2001/XMLSchema" target="_blank"&gt;http://www.w3.org/2001/XMLSchema&lt;/A&gt;"&amp;gt;&lt;BR /&gt; &amp;lt;requestAdditionalAttributes&amp;gt;&lt;BR /&gt; &amp;lt;additionalAttribute name="senderEmail" value="email@example.com"/&amp;gt;&lt;BR /&gt; &amp;lt;/requestAdditionalAttributes&amp;gt;&lt;BR /&gt;&amp;lt;/ns0:operationAdditionalData&amp;gt;&lt;BR /&gt;[user@server]$ curl --tlsv1.1 -v -k -X 'PUT' -H "Content-Type: application/xml" -d @xml.xml 'https://sponsor:XXX@1.1.1.1:9060/ers/config/guestuser/email/31e8ca71-f49e-11e8-bc83-2e9d9d140649/portalId/36a96010-c267-11e8-89ad-2e2e02dc7046'&lt;/P&gt;
&lt;P&gt;ERROR: &amp;lt; HTTP/1.1 415 Unsupported Media Type&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Header "Content-Type: application/json"&lt;/STRONG&gt;&lt;BR /&gt;[user@server]$ curl --tlsv1.1 -v -k -X 'PUT' -H 'Content-Type: application/json' -d '{"OperationAdditionalData":{"additionalData":[{"name":"senderEmail","value":"email@example.com"}]}}' 'https://sponsor:XXX@1.1.1.1:9060/ers/config/guestuser/email/31e8ca71-f49e-11e8-bc83-2e9d9d140649/portalId/36a96010-c267-11e8-89ad-2e2e02dc7046'&lt;BR /&gt;ERROR: &amp;lt; HTTP/1.1 415 Unsupported Media Type&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Header "Content-Type: application/json" “ACCEPT: application/json”&lt;/STRONG&gt;&lt;BR /&gt;[user@server]$ curl --tlsv1.1 -v -k -X 'PUT' -H 'ACCEPT: application/json' -H 'Content-Type: application/json' -d '{"OperationAdditionalData":{"additionalData":[{"name":"senderEmail","value":"email@example.com"}]}}' 'https://sponsor:XXX@1.1.1.1:9060/ers/config/guestuser/email/31e8ca71-f49e-11e8-bc83-2e9d9d140649/portalId/36a96010-c267-11e8-89ad-2e2e02dc7046' &lt;BR /&gt;ERROR: &amp;lt; HTTP/1.1 500 Internal Server Error&lt;BR /&gt;&amp;lt; Server:&lt;BR /&gt;&amp;lt;&lt;BR /&gt;{&lt;BR /&gt; "ERSResponse" : {&lt;BR /&gt; "operation" : "PUT-email-guestuser",&lt;BR /&gt; "messages" : [ {&lt;BR /&gt; "title" : "Email request for GuestUser with ID (31e8ca71-f49e-11e8-bc83-2e9d9d140649) failed due to Error while generating Email ",&lt;BR /&gt; "type" : "ERROR",&lt;BR /&gt; "code" : "CRUD operation exception"&lt;BR /&gt; } ],&lt;BR /&gt; "link" : {&lt;BR /&gt; "rel" : "related",&lt;BR /&gt; "href" : "&lt;A href="https://1.1.1.1:9060/ers/config/guestuser/email/31e8ca71-f49e-11e8-bc83-2e9d9d140649/portalId/36a96010-c267-11e8-89ad-2e2e02dc7046" target="_blank"&gt;https://1.1.1.1:9060/ers/config/guestuser/email/31e8ca71-f49e-11e8-bc83-2e9d9d140649/portalId/36a96010-c267-11e8-89ad-2e2e02dc7046&lt;/A&gt;",&lt;BR /&gt; "type" : "application/xml"&lt;BR /&gt; }&lt;BR /&gt; }&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;HEADER "Content-Type: application/vnd.com.cisco.ise.identity.guestuser.2.0+xml"&lt;/STRONG&gt;&lt;BR /&gt;[user@server]$ curl --tlsv1.1 -v -k -X 'PUT' -H "Content-Type: application/vnd.com.cisco.ise.identity.guestuser.2.0+xml" -d @xml.xml 'https://sponsor:XXX@1.1.1.1:9060/ers/config/guestuser/email/31e8ca71-f49e-11e8-bc83-2e9d9d140649/portalId/36a96010-c267-11e8-89ad-2e2e02dc7046'&lt;BR /&gt;ERROR: &amp;lt; HTTP/1.1 415 Unsupported Media Type&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 08:52:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-api-header-to-send-email-to-guests/m-p/3755960#M543529</guid>
      <dc:creator>thiagosilvino</dc:creator>
      <dc:date>2019-03-11T08:52:36Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 API header to send email to guests</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-api-header-to-send-email-to-guests/m-p/3768155#M543530</link>
      <description>&lt;P&gt;Below worked for me.&lt;/P&gt;
&lt;P&gt;
&lt;PRE&gt;
&lt;CODE&gt;curl -X PUT -k -H 'Content-Type: application/json' -H 'Accept: application/json' -i 'https://mySponsor:mySponsorPassword@myISE:9060/ers/config/guestuser/email/11c276c0-05b4-11e9-a436-005056abd9c7/portalId/40963c00-2e02-11e8-ba71-005056872c7f' --data '{
  "OperationAdditionalData" : {
    "additionalData" : [ {
      "name" : "senderEmail",
      "value" : "sponsor@demo.local"
    } ]
  }
}'
&lt;/CODE&gt;
&lt;/PRE&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 23 Dec 2018 01:38:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-api-header-to-send-email-to-guests/m-p/3768155#M543530</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2018-12-23T01:38:40Z</dc:date>
    </item>
  </channel>
</rss>

