Bug ID 749161: Problem sync policy contains non-ASCII characters

Last Modified: Nov 14, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP APM(all modules)

Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2

Fixed In:
15.0.0,, 13.1.3

Opened: Nov 07, 2018
Severity: 3-Major


When access policy contain non-ASCII characters, policy sync either fails or the characters are not sync'ed properly on the target.


Policy sync fails or does not complete properly for the non-ASCII characters.


-- Using an access profile. -- Access profile contains non-ASCII characters (code point greater than 0x7f), e.g.,in VPE, add an 'Advanced Resource Assign' agent and specify an expression similar to the following in addition to the resource: expr { [string tolower [mcget -decode {session.ad.last.attr.memberOf}]] contains [string tolower "CN=Suporte_TransmissãCo,"] || [string tolower [mcget -decodde {session.ad.last.attr.memberOf}]] contains [string tolower "CN=suporte_tx,"]} -- Start policy sync on the profile.



Fix Information

Policy sync now works properly when the policy contains non-ASCII characters.

Behavior Change