Setting up P4 authentication

Before you set up P4 authentication, make sure you review P4 authentication prerequisites.

The following information explains how to set up your P4 DAM instance with P4 Server authentication, which is required.

An unlicensed P4 Server is limited to 10 repositories. For more information, see P4 Server Licenses, which includes a license for P4 Server.

For additional information about P4 authentication:

After you configure P4 authentication and the P4 DAM instance is in use, you cannot revert to a different authentication method.

  1. Log in to the Perforce TeamHub administrator UI. See Logging in to the TeamHub admin UI.

  2. When prompted, enter your license information and click Apply.

  3. Click Preferences.

    The Preferences page opens.

    Some options in Preferences are dependent on others and are only displayed if required. For example, the option to add fingerprints is only displayed if TeamHub detects a P4PORT value that starts with SSL.

  4. Enter the Hostname of your TeamHub instance.

  5. In the Authentication section, click Helix.

  6. In the P4 Server section, enter or select information in each area:

    • P4PORT value - The host (name or IP address) and port for the P4 Server, in the following format: host:port.

    • Fingerprint - If you connect to P4 Server using an SSL/TLS connection, add a fingerprint of the key received for SSL/TLS connections. If the fingerprint changes (or expires), you can add more fingerprints and delete outdated fingerprints. This is the equivalent of running the p4 trust command in the P4 command line. For details, see the P4 CLI Reference.

      Deleting a fingerprint configured for the port removes the trust established with P4 Server. As a result, everything in TeamHub stops working against the respective SSL/TLS port.
    • P4 integration user
      • Username - Enter the username of an existing P4 Server user with super privileges. This user must have unlimited ticket timeout. For P4 Server 2025.1 and later, the integration user must also have an unlimited idle timeout.
        • You cannot change a username (or email address) in P4 Server. Instead, you need to make this change on the P4 Server side and wait for the sync.

        The P4 integration user does not count against your TeamHub license plan seats, but each user requires a background license. To request background licenses, use the Background user request form on the Perforce website.

      • Ticket/Password - The password/ticket for the existing P4 Server user with super level privileges. The existing P4 Server user must be a member of a group that has an unlimited timeout set for the session and password. For P4 Server 2025.1 and later, the integration user must also have an unlimited idle timeout. See Create a super user on the P4 Server.

      • Charset - Select the character encoding set for P4 Server, such as utf8 or none. To find the P4 Server charset, run: p4 -ztag info. When connecting to a non-unicode server, the charset is none by default. If the charset is not shown, select none from the list. For more information on P4 Server charsets, run: p4 help charset

    • Account and group synchronization

  7. Click Test Helix Core connection and wait for a message to be displayed: Successfully connected to P4.

  1. Click Save preferences.

    A warning is displayed because the changes have not been applied to the server yet.

  2. Click Run reconfigure to apply the server configuration changes. See Reconfiguring P4 DAM to apply server configuration changes.

    3. Failure to click Run reconfigure may result in normal web server interruption messages, such as the HTTP Error 503. The service is unavailable. error, because the services come back online.