Hello!
We plan to introduce Dynamic ID. We use certificate-based authentication as the first factor and dynamic_id as the second factor.
Our problem was that the full DN in the Subject field of the certificate contains a space (0x20) character. This is likely to cause problems parsing the $CPDIR/conf/dynamic_id_users_info.lst file.
What we tried but didn't work:
- we put the full DN field in quotation marks
- we tried to protect the space with a backslash character (\ )
- certificates do not have a SAN field, so the e-mail address in the SAN field is also out of the question
- no AD/LDAP integration
Any other idea?
Thanks,
ps: gw R81.20