8000 Merge pull request #50 from Hacker0x01/credential-management · hacker0x011/docs.hackerone.com@34a235a · GitHub
[go: up one dir, main page]
S 8000 kip to content

Commit 34a235a

Browse files
stacyspivastacyspiva
authored
Merge pull request Hacker0x01#50 from Hacker0x01/credential-management
changes
2 parents 3a1d436 + 7ee783e commit 34a235a

File tree

2 files changed

+31
-35
lines changed

2 files changed

+31
-35
lines changed

‎docs/programs/api-tokens.md

Lines changed: 30 additions & 34 deletions
Original file line numberDiff line numberDiff line change
@@ -1,34 +1,30 @@
1-
---
2-
title: "API Tokens"
3-
path: "/programs/api-tokens.html"
4-
id: "programs/api-tokens"
5-
---
6-
7-
Your program’s administrative users can generate and manage API tokens to experiment with or use the HackerOne API. The API token identifier and value are used as the username and password for HTTP Basic authentication.
8-
9-
To generate an API token:
10-
1. Go to <b>Settings > Program > Automation > API</b>.
11-
! 10000 [api-token-1](./images/api-token-1.png)
12-
13-
2. Click <b>Create API Token</b>.
14-
![api-token-2](./images/api-token-2.png)
15-
16-
3. Enter an identifier for the new API token.
17-
![api-token-3](./images/api-token-3.png)
18-
19-
4. Store the generated API token.
20-
5. Click <b>I have stored the API Token</b>.
21-
![api-token-4](./images/api-token-4.png)
22-
23-
You’ll get a confirmation email stating that you’ve created a new API token. You can manage the groups that have access to the API tokens and revoke the token as well.
24-
25-
To learn more about the HackerOne API check out our [API docs](https://api.hackerone.com/docs/v1).
26-
27-
### Managing Groups
28-
To manage which groups have access to the API tokens:
29-
1. Click <b>Manage groups</b> on the API settings page for the identifier you want to manage groups for.
30-
![api-token-5](./images/api-token-5.png)
31-
32-
2. Select which groups you want to give permissions to. When a group isn’t selected, they only have read-only permissions.
33-
3. Click <b>Apply changes</b>.
34-
![api-token-6](./images/api-token-6.png)
1+
---
2+
title: "API Tokens"
3+
path: "/programs/api-tokens.html"
4+
id: "programs/api-tokens"
5+
---
6+
7+
Your program’s administrative users can generate and manage API tokens to experiment with or use the HackerOne API. The API token identifier and value are used as the username and password for HTTP Basic authentication.
8+
9+
To generate an API token:
10+
1. Go to <b>Settings > Program > Automation > API</b>.
11+
![api-token-1](./images/api-token-1.png)
12+
13+
2. Click <b>Create API Token</b>.
14+
15+
3. Enter an identifier for the new API token.
16+
![api-token-3](./images/api-token-3.png)
17+
18+
4. Store the generated API token.
19+
5. Click <b>I have stored the API Token</b>.
20+
![api-token-4](./images/api-token-4.png)
21+
22+
You’ll get a confirmation email stating that you’ve created a new API token. You can manage the groups that have access to the API tokens and revoke the token as well.
23+
24+
To learn more about the HackerOne API check out our [API docs](https://api.hackerone.com/docs/v1).
25+
26+
### Managing Groups
27+
To manage which groups have access to the API tokens:
28+
1. Click <b>Manage groups</b> on the API settings page for the identifier you want to manage groups for.
29+
2. Select which groups you want to give permissions to. When a group isn’t selected, they only have read-only permissions.
30+
3. Click <b>Apply changes</b>.

‎docs/programs/credential-management.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ path: "/programs/credential-management.html"
44
id: "programs/credential-management"
55
---
66

7-
The Credential Management feature enables you to pre-populate the credentials to access your assets on HackerOne. This enables participating hackers to quickly retrieve the credentials needed to find vulnerabilities in your program.
7+
The Credential Management feature enables you to easily share access credentials with hackers so that you don't have to constantly create sign in credentials for each new hacker that participates in your program. This also enables participating hackers to quickly retrieve the credentials needed to find vulnerabilities in your program.
88

99
<i>This feature is currently in beta and only available to select programs.</i>
1010

0 commit comments

Comments
 (0)
0