Forum Discussion
mikegray_198028
Cirrus
Oct 11, 2016certificate signature failure
Hello,
Any idea about the below error, when we enable client authentication on particular client ssl profile, we are facing this error but the same bundle is working with other profiles
warning ...
Anthony_Graber
Employee
Oct 11, 2016Which version of TMOS are you running on your BIG-IP? Have you tried using this solution article on Askf5 to troubleshoot client authentication? https://support.f5.com/kb/en-us/solutions/public/14000/800/sol14819.html
Error code 42 is listed as bad_certificate:The certificate was corrupt or contained signatures that could not be correctly verified. This alert can occur if the client certificate was signed by a different CA than the one specified in the SSL profile.
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects