Authenticating to a Client-Side SSL realm may prompt to select certificate several times

Follow
    Applies to:
  • SecureAuth Identity Platform
  • Legacy SecureAuth IdP
Deployment model:
  • Cloud
  • Hybrid
  • On Premises
  • Version Affected:  All

    Description:  

    Authenticating to a cSSL realm may prompt to select the certificate three to six times before the authentication is fully successful.

     

    Cause:  

    Requiring client certificates on the full realm may cause the prompting when using Firefox or Safari browsers due to their security preferences.

     

    Resolution:  

    The steps below will show how to configure the cSSL realm if this issue is found in the environment.

    Open IIS Manager

    Expand the Server

    Expand Sites

    Expand Default Web Site

    Select the Realm which is having the cSSL issue.

    mceclip0.png

     

    With the realm selected

    Double click the 'SSL Settings' in the middle pane, under the IIS section

    mceclip2.png

     

    Under the 'Client certificates' section, select 'Ignore'

    On the right side under the Action Pane, click 'Apply'

    mceclip3.png

     

    Click the realm again

    In the lower bar of the middle section, click 'Content View'

    mceclip4.png

     

    Find the file cSSL.aspx

    Right click and select 'Switch to Features View'

    mceclip5.png

     

    The middle section will show that you are editing cSSL.aspx

    Double click the 'SSL Settings' in the middle pane

    mceclip6.png

     

    Set the 'Client certificates' to 'Require'

    Click 'Apply' in the actions pane on the right.

     

    Test to ensure the changes to the settings has worked and end-users only require selecting their Client Certificate once to authenticate

    mceclip7.png

     

     

    SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

    Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.

    0 out of 0 found this helpful

    Comments

    0 comments

    Please sign in to leave a comment.