cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1646
Views
10
Helpful
8
Replies

ISE 1.3 SMS configuration

eng__mohamed
Level 1
Level 1

When i try to configure SMS gateway configuration on ISE ,  i received this message when i configure Data (Url encoded portion):

 

An exception occurred during the creation of a sms profile. Request not processed - Possible XSS input 

 

Kindly advise 

2 Accepted Solutions

Accepted Solutions

Hi Mohamed,

URL encoded portion does not support UTF-8 or UTF-64 encoding patterns. I does only support plain text. An enhancement request for support of encoding formats in filed on ISE 1.3 version.

 

Thanks,

Naresh

View solution in original post

Hi Mohamed,

 

ISE 1.3 does not support UTF-8 or UTF-16 encoding for SMS URL Encoding. Let me check and get you the defect ID for this.

 

Thanks,

Naresh

View solution in original post

8 Replies 8

eng__mohamed
Level 1
Level 1

i use the below config in Data (Url encoded portion): but still same error 

An exception occurred during the creation of a sms profile. Request not processed - Possible XSS input 

 

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <send xmlns="http://********/api/sms">
     <UserName>*********</UserName>
      <PassWord>*********</PassWord>
      <SenderName>*******</SenderName>
      <MobileNo>$mobilenumber$</MobileNo>
      <Msg>$message$</Msg>
    </send>
  </soap:Body>
</soap:Envelope>

 

Hi Mohamed,

URL encoded portion does not support UTF-8 or UTF-64 encoding patterns. I does only support plain text. An enhancement request for support of encoding formats in filed on ISE 1.3 version.

 

Thanks,

Naresh

hi nginjupa

i already run V 1.3 

till now wait TAC reply 

 

Hi Mohamed,

 

ISE 1.3 does not support UTF-8 or UTF-16 encoding for SMS URL Encoding. Let me check and get you the defect ID for this.

 

Thanks,

Naresh

Hi Naresh,

 

We have a problem with SMS notification. Please find the attached snapshot of current SMS email gateway configuration. Guest is receiving notification when I am providing the exact mobile number instead of 974$mobilenumber$ in SMTP API destination address: field.

 

We are running ISE 1.3 with patch level 2.

We are using the  the default option (Global Default) SMS Gateway providers for our configuration rather creating a custom. Any luck??

 

Hi Mohammed,

Any luck in ISE/SMS configuration? I am experiencing same issue. We are running 1.4 and i am getting same msg "possible XSS input..."

Our gateway supports WSDL "http://webxyz/smszy/SMSS.asmx?WSDL"

Thanks

mohanak
Cisco Employee
Cisco Employee
% Character in Evaluate Configuration Validator not Escaped
CSCuj71682

Symptom:
The message "HTTP Status 400 - Request not processed - Possible XSS input: null" is seen when attempting to validate the NAD's configuration with the Evaluate Configuration Validator tool.

Conditions:
This occurs when there is a '%' sign in the password used, except when it is the first character.

Workaround:
Avoid using '%' as anything other than the first character in a NAD password where the Configuration Validator is to be used.

 

Known Affected Releases:
(2)
1.2(0.899)
1.3(0.638)

I think this not related to my case as this SMS configuration not NAD config 

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: