Appearance

Powered by Platform One

Product Team Application Access Guide ​

Overview ​

Use this guide to understand the processes users need to follow to access your Party Bus application in the IL2, IL4, and IL5 staging and production environments, as well as the platform tools.

Initial Access ​

All users must self-register for a P1 account here.

Zero Trust Access Requirements ​

P1 requires the use of Zero Trust SDP Appgate for access to all IL4 and IL5 applications. You must use one of the following Appgate options:

  • Install the full client software on their computer, or
  • Use the web proxy version, called Appgate Portal.

By default, Party Bus implements DNS routing to ensure all IL4 staging/production applications are behind the Appgate Portal. Please submit a C1 Appgate Portal Request to the P1 Help Desk if the use of the full client is desired for IL4. Per P1 cybersecurity policy, access to all IL5 applications requires the use of Appgate full client software.

For those accessing Party Bus IL4 and IL5 applications from within the DoDIN, P1 has implemented either the use of Appgate Portal or an Appgate whitelist (exceptions). While P1 does not routinely offer whitelisting for Appgate, customers with a valid mission need may work with the P1 Help Desk to navigate the formal CNAP approval process by submitting a C1 Zero Trust Bypass Request . IP whitelisting is a last-resort option, and is only available for:

  • GFE devices,
  • Users who need NIPR network IL4 access only (not IL5 or IL6), or
  • Users who cannot install the Appgate client due to policy or technical restrictions.

For more information, please review the CNAP Access and Connectivity documentation. This strategy ensures compliance with DoW and Department of the Air Force mandates to implement Zero Trust technology by 2027 to improve the DoW’s cybersecurity posture. For those accessing from the internet (outside the DoDIN), the use of Appgate Portal (for IL4) or Appgate full client (for IL4 or IL5) is required. For further documentation regarding the use of Appgate, you can also review CNAP’s documentation site.

NOTE

The MDO team can only grant access to Argo CD, GitLab SAST, and SonarQube. For all other access requests, please submit a P1 Help Desk , or send an email to aflcmc.hncx.helpdesk@us.af.mil.

ILX Authorized Access ​

Have your designated team lead/OS complete the Application Access Update Help Desk Request to request and grant your access.

  • In the form, your team lead will request what type of access is needed (i.e., Jira, Confluence, Mattermost, GitLab, and/or IL deployment environment).
    • For IL deployment environments, team leads must include a DD2875.
  • Product Team Leads: To add new users to the P1 Mattermost space, click ≡ → Invite People → Add members. This will allow members to see all public P1 Mattermost channels.

IL2 Staging and Production Environment ​

To view your application in IL2 staging and production, users will need the following:

No P1 account is required.

IL4 Staging and Production Environment ​

To view your application in IL4 staging and production, users will need the following:

  • A P1 account, and
  • To be IL4-authorized. IL4 authorization is granted via a CAC. Users must log in with their CAC. Guidance for logging in with a CAC can be found here.

IL5 Staging and Production Environment ​

To view your application in IL5 staging and production, users will need the following:

  • A P1 account,
  • To be IL5-authorized. IL5 authorization is granted via a CAC; and
  • AppGate. For more information, please refer to the P1 CNAP AppGate SDP Client.

Party Bus Tool Access ​

Developers will have high-level GitLab access after acquiring ILX Authorized Access. Product team leads must grant any additional or application-specific access by adding new users to the appropriate GitLab groups.

Join the Party Bus Value Stream Support Channel for support via Mattermost.

MDO Tool Access ​

ASSUMPTION

All team members have been granted ILX/GITLAB, ILX ATLASSIAN, ILX MATTERMOST Keycloak groups for access to the basic P1 tools.

If your application is being onboarded to Party Bus: ​

Add a comment to your application’s COT project with a list of emails for the developers who need access to the tools below. This is required by the MDO team.

If your application is already running in Party Bus and you’d like to provision access for a new developer: ​

Tools ​

SonarQube ​

Access is granted to the same IL as the application’s code repository.

GitLab SAST ​

Access is granted to the same IL as the application’s code repository.

Argo CD ​

Users will already be able to access Argo CD in whichever IL they have access to. However, MDO must add users to specific groups that determine what users can view within Argo CD. All developer users, regardless of IL, will be added to the same access groups and have the same permissions (i.e., all developers will have the same IL2 view or IL4 view).

Before logging into Argo CD, users must onboard their device by following the instructions to install the CNAP AppGate SDP Client. This application must be running for the user to access Argo CD.

NOTE

Product teams are not granted access to the Twistlock UI, Trufflehog, or Anchore. Failures for these are only viewable in pipeline logs.

Done ​

Celebrate! You should have access to the applications you need.

Related Content and References ​

Submit Requests to the Help Desk and Get Support ​

Access Required Services ​

Review Supporting Documentation ​

Powered By Platform One