Getting Started

Individuals who have a valid authorized need to access DoD Public Key Infrastructure (PKI)- protected information but do not have access to a government site or government-furnished equipment will need to configure their systems to access PKI-protected content.

Accessing DoD PKI-protected information is most commonly achieved using the PKI certificates stored on your Common Access Card (CAC). The certificates on your CAC can allow you to perform routine activities such as accessing OWA, signing documents, and viewing other PKI-protected information online. For more information about your CAC and the information stored on it, visit http://www.cac.mil.

Before you begin, make sure you know your organization’s policies regarding remote use.

To get started you will need:

You can get started using your CAC by following these basic steps:

  1. Get a card reader.
    At this time, the best advice for obtaining a card reader is to work with your home component to get one. In addition, please review the CAC smart card reader requirements for more information regarding the requirements for a card reader.
  2. Install middleware, if necessary.
    You may need additional middleware, depending on the operating system you use. Please contact your CC/S/A for more information on the middlew​are requirements for your organization. You can find their contact information on our Help page tab.
  3. Install DoD root certificates with InstallRoot (32-bit, 64-bit or Non Administrator)
    In order for your machine to recognize your CAC certificates and DoD websites as trusted, run the InstallRoot utility (32-bit, 64-bit, or Non Administrator) to install the DoD CA certificates on Microsoft operating systems. If you’re running an alternate operating system such as Mac OS or Linux, you can import certificates from the PKCS 7 bundle. The InstallRoot User Guide is available here.
  4. Make certificates available to your operating system and/or browser, if necessary.
    Pick your browser for specific instructions.

To get started you will need:

You can get started using your CAC on your Mac OS X system by following these basic steps:

  1. Get a card reader
    Typically Macs do not come with card readers and therefore an external card reader is necessary. At this time, the best advice for obtaining a card reader is through working with your home component. In addition, please review the CAC smart card reader requirements for more information regarding card reader requirements.
  2. Download and install the OS X Smartcard Services package
    The OS X Smartcard Services Package allows a Mac to read and communicate with a smart card. In order for your machine to recognize your CAC certificates and DoD websites as trusted, the installer will load the DoD CA certificates on OS X. Please refer to this page for specific installation instructions.
  3. Address the cross-certificate chaining Issue
    These instructions walk through adjusting the trust settings on the Interoperability Root CA (IRCA) > DoD Root CA 2 and the US DoD CCEB IRCA 1 > DoD Root CA 2 certificates to prevent cross-certificate chaining issues. This can make it appear that your certificates are issued by roots other than the DoD Root CA 2 and can prevent access to DoD websites.
  4. Configure Chrome and Safari, if necessary
    Safari and Google Chrome rely on Keychain Access properly recognizing your CAC certificates.
    1. In Finder, navigate to Go > Utilities and launch KeychainAccess.app
    2. Verify that your CAC certificates are recognized and displayed in Keychain Access

    Keychain Access

    Note: CACs are currently made of different kinds of card stock. To determine what card stock you have, look at the back of your CAC above the magnetic strip. Most CACs are supported by the Smartcard Services package, however Oberthur ID One 128 v5.5 CACs are not. Third party middleware is available that will support these CACS; two such options are Thursby Software’s PKard and Centrify’s Express for Smart Card.

    To get started you will need:

    You can get started using your CAC with Firefox on Linux machines by following these basic steps:

    1. Get a card reader.
      At this time, the best advice for obtaining a card reader is to work with your home component to get one. In addition, please review the CAC smart card reader requirements for more information regarding the requirements for a card reader.
    2. Obtain middleware.
      You will need middleware for Linux to communicate with the CAC. The CoolKey PKCS#11 module provides access to the CAC and can be installed using Linux package management commands.
      • For Debian-based distributions, use the command apt-get install coolkey
      • For Fedora-based distributions, use the command yum install coolkey. The CoolKey PKCS #11 module version 1.1.0 release 15 ships with RHEL 5.7 and above and is located at /usr/lib/pkcs11/libcoolkeypk11.so.

    Next Steps

    Your internet browser is now configured to access DoD websites using the certificates on your CAC. Now that your machine is properly configured, please login and visit our End Users page for more information on using the PKI certificates on your CAC.

    The DoD Cyber Exchange is sponsored by
    Defense Information Systems Agency (DISA)

    U.S. Government Notice and Consent

    You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.

    By using this IS (which includes any device attached to this IS), you consent to the following conditions:

    · The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations.

    · At any time, the USG may inspect and seize data stored on this IS.

    · Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG authorized purpose.

    · This IS includes security measures (e.g., authentication and access controls) to protect USG interests – not for your personal benefit or privacy.

    Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.