cancel
Showing results for 
Search instead for 
Did you mean: 

Cannot perform client authentication: Have no certificate fitting to CA names received from server

Former Member
0 Kudos

Dear experts,

I have problems with implementation SSO 3.0 with secure login server and x509 certificates.

I installed secure login server 3.0 SP1 and integrated it in the existing KPI infraestructure with USER CA certificate.

I exported the certificate and imported it in the Certificate Management, afterwards I imported it the client machine and downloaded the policy SecureLoginDefaultGroup and installed it in the client machine, but when I tried to login into the secure login client, the following certificate error appears:

Supplied credentials not accepted by the server.

The secure login client trace shows the following info:

[2017.04.05 13:10:11.287000][3][sbus.exe ][SSL ][ 3724] Cli-0000000E: Server sent 4 trusted CA name(s) for client authentication [2017.04.05 13:10:11.288000][3][sbus.exe ][SSL ][ 3724] Cli-0000000E: Cannot perform client authentication: Have no certificate fitting to CA names received from server [2017.04.05 13:10:11.288000][3][sbus.exe ][SSL ][ 3724] Cli-0000000E: Sending message with empty certificate list [2017.04.05 13:10:11.288000][3][sbus.exe ][SSL ][ 3724] Cli-0000000E: Sending empty Certificate message. [2017.04.05 13:10:11.292000][3][sbus.exe ][SSL ][ 3724] Cli-0000000E: ########## TLSv1.2 connection with this server established: CN=XXX.XXX.com, C=ES ##########

Could you help us with this error?

Thank you

Regards

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hello,

I updated to the las sp and then works!

Regards

Answers (2)

Answers (2)

Former Member
0 Kudos

Hello.

I have the same problem. Please, could you tell me if you were able to solve this problem?

Is there any parameter in ICM to force sending the client certificate?

Thank you very much,.

Former Member
0 Kudos

Hi Saul,

I am getting the same error.

Were you able to resolve? Please suggest. Thanks.

Regards,

Prateek