For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

X509 Subject Formatting

Problem this snippet solves: TMOS v12.1.4.1 and v13 have a change where the output of X509::subject is formatted to match OpenSSL output. See https://cdn.f5.com/product/bugtracker/ID607410.html ...
Published Oct 18, 2019
Version 1.0
application delivery
iRules
TMOS
X509 SSL
PeteWhite's avatar
Icon for Employee rankEmployee
I work in the EMEA F5 Professional Services team. I generally deal Service Provider stuff because i come from that background ( 12 years working for Nokia Networks prior to joining F5 in 2013 )
View Profile
PeteWhite's avatar
Icon for Employee rankEmployee
I work in the EMEA F5 Professional Services team. I generally deal Service Provider stuff because i come from that background ( 12 years working for Nokia Networks prior to joining F5 in 2013 )
View Profile
uniqng's avatar
uniqng
Icon for Altostratus rankAltostratus
Nov 20, 2019

It works but there's just one small issue (might be a bug?). BTW my version is 13.1.3 build 0.0.6

 

Here's the relevant code

  

set subject [regsub -all {(".*),(.*")} $subject "\\1--COMMA--\\2"]
 
log local0. "Comma replaced: $subject"

 

 

In case there are 2 fields with commas in the subject it only replaces second comma occurrence inside double-quotes. This is what I get

 

Nov 20 01:24:26 example.lab info tmm5[12408]: Rule /Common/irule-subject-reverse <HTTP_REQUEST>: Original Subject: C=GB, ST="London, City of", L=Bar, O=Foo, OU=TEST, CN="F5lab, local"

Nov 20 01:24:26 example.lab info tmm5[12408]: Rule /Common/irule-subject-reverse <HTTP_REQUEST>: Comma replaced: C=GB, ST="London, City of", L=Bar, O=Foo, OU=TEST, CN="F5lab--COMMA-- local"

 

I believe the regsub -all option should replace all the occurrences of the comma(,) in the string right?

 

Any ideas what might be wrong?