HackerOne Code
Visit HackerOne.comLog In
  • Introduction to HackerOne Code for On-Premise Integrations
  • Create User Account & Organization
  • Installing PullRequest Proxy
  • Configuring your Proxy to Connect to the PullRequest Server
  • Configure Posting User
    • Configure GitHub Posting User
    • Configure Bitbucket Posting User
    • Configure GitLab Posting User
    • Configure Azure DevOps Posting User
  • Configuring SSL
  • Start the PullRequest Proxy
  • Verify Data on HackerOne Code
  • Configure Webhooks
    • Configure GitHub Webhooks
    • Configure Bitbucket Webhooks
    • Configure GitLab Webhooks
    • Configure Azure DevOps Webhooks
  • Next Steps
    • Project Visibility in the HackerOne Code Dashboard
  • Manually Requesting Validation With Posting User
  • Upgrading PullRequest Proxy
  • PullRequest Proxy Dataflow Diagram
Powered by GitBook
On this page
  • Register on the HackerOne Code Platform
  • Organization Roles
  • Your Organization

Create User Account & Organization

Creating an organization is the first step for the PullRequest Proxy integration. In order to create the organization, we'll need to be able to associate it with at least 1 active user account.

PreviousIntroduction to HackerOne Code for On-Premise IntegrationsNextInstalling PullRequest Proxy

Last updated 27 days ago

Register on the HackerOne Code Platform

Any individuals from your team who will be assisting in the integration of PullRequest Proxy with your GitHub Enterprise, Bitbucket Server, or GitLab Self-Managed instance will first need to with PullRequest.

Be sure the emails used to create these accounts have an email address with your company's domain.

Example:

name@companyname.com

If the users will have email domains that vary, but still belong to your organization, please send a list of those domains to your HackerOne point of contact.

Organization Roles

PullRequest organizations consist of team members with Member roles and Owner roles - of which they may be multiple of each.

To create an organization there must be at least 1 user with an Owner role. Otherwise, our system will automatically select the first registered user with your approved email domain with an Owner role. This may be transferred at any time.

Permissions by Role

Permission

Member

Owner

View connected repositories and open code reviews

✔

✔

Manually initiate scans and validation

✔

✔

Leave feedback on code reviews posted by HackerOne engineers

✔

✔

View organization's team members

✔

✔

Cancel active HackerOne Code review jobs

✔

✔

View HackerOne Code scan & validation statuses as well as history

✔

✔

Add team members to the organization

--

✔

Install the PullRequest Proxy

--

✔

Connect the PullRequest Proxy with on-premise GitHub, Bitbucket or GitLab

--

✔

Add a required posting or service user to on-premise GitHub, Bitbucket or GitLab

--

✔

Configure webhooks

--

✔

Your Organization

Your HackerOne Code organization will be created by a HackerOne staff member - and the registered user accounts you specify will be added to it. Your company name will be used by default. If you have a specific name you'd like to call the organization please let your HackerOne point of contact know.

create an account