Symantec Access Management

Tech Tip : CA Single Sign-On : CA SSO SQL Server Wire Protocol not present in ODBCcad

  • 1.  Tech Tip : CA Single Sign-On : CA SSO SQL Server Wire Protocol not present in ODBCcad

    Broadcom Employee
    Posted Oct 08, 2018 03:58 AM

    Issue:


    We're configuring Policy Server, when we open the OS ODBC pane, we
    find no CA Single Sign_on SQL Server Wire Protocol present. The

    drivers present are Microsoft's only.

     

    We've configured the ODCB for Policy Server 12.8 that way :

     

    1. Complete one of the following steps:
    If you are using a supported 64–bit Windows operating system:
    Navigate to C:\Windows\SysWOW64.
    Double–click odbcad32.exe.

     

    2. The ODBC Data Source Administrator appears
    Click the System DSN tab.
    System data source settings appear.
    Click Add.

     

    3. The Create New Data Source dialog appears.
    Select CA Single Sign-On SQL Server Wire Protocol and click Finish.
    The ODBC SQL Server Wire Protocol Driver Setup dialog appears.

    But as said, at this state we don't see the CA Single Sign-On drivers.

     

    Cause:

     

    You get this issue because you're using the ODBC 32bit and Policy
    Server 12.8 requires the 64bit as it is a 64bit process as described
    in the documentation :

     

    Configure an Oracle Data Source for CA Single Sign-On

     

    Create an Oracle Data Source on Windows

     

    Follow these steps:

     

    Click Start and navigate to Programs, Administrative Tools.

    Select ODBC Data Sources (64-bit).

    The ODBC Data Source Administrator dialog opens.

    Click the System DSN tab and click Add.
    The Create New Data Source dialog appears

    [...]

    https://docops.ca.com/ca-single-sign-on/12-8/en/installing/install-a-policy-server/configure-odbc-databases-as-policy-session-key-and-audit-stores/configure-an-odbc-database-as-a-policy-store/how-to-configure-an-oracle-policy-store

     

    Resolution:

     

    Uses the 64bit ODBC Data Source to solve this issue;

     

    KB : KB000117071