Forum Discussion
Dev_56330
Dec 14, 2015Cirrus
The thought from a fellow F5 administrator is that the Big IP is still unable to properly present a certificates SN which should have been resolved in BIGIP-9.3.0 per the notes in the article below. I personally cannot replicate this issue and I don't even know that I fully understand what or how he is attempting this type of authentication though he describes the issue just as it states in the article where the order of the Subject Name is reversed.
Note
There is a behavior change since BIGIP-9.3.0 for this command to support multiple languages and RFC 2253 compliance.
Before the change
1
/CN=Name/OU=UNIT/O=ORG/C=US
After the change
1
C=US,O=ORG,OU=UNIT,CN=NAME
https://clouddocs.f5.com/api/irules/X509__issuer.html