Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
847f20b2
Commit
847f20b2
authored
Sep 14, 2020
by
Michael Eddington
Committed by
Nick Gaskill
Sep 14, 2020
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Document use of environment_url.txt in API Fuzzing
parent
99ba0b38
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
24 additions
and
2 deletions
+24
-2
changelogs/unreleased/241206-environmenturl-api-fuzzing-docs.yml
...ogs/unreleased/241206-environmenturl-api-fuzzing-docs.yml
+5
-0
doc/user/application_security/api_fuzzing/index.md
doc/user/application_security/api_fuzzing/index.md
+19
-2
No files found.
changelogs/unreleased/241206-environmenturl-api-fuzzing-docs.yml
0 → 100644
View file @
847f20b2
---
title
:
Add support for environment_url.txt to API Fuzzing
merge_request
:
41523
author
:
type
:
added
doc/user/application_security/api_fuzzing/index.md
View file @
847f20b2
...
...
@@ -107,7 +107,15 @@ Follow these steps to configure API fuzzing in GitLab with an OpenAPI specificat
```
1.
The target API instance's base URL is also required. Provide it by using the
`FUZZAPI_TARGET_URL`
variable:
variable or an
`environment_url.txt`
file.
Adding the URL in an
`environment_url.txt`
file at your project's root is great for testing in
dynamic environments. To run API fuzzing against an app dynamically created during a GitLab CI/CD
pipeline, have the app persist its domain in an
`environment_url.txt`
file. API fuzzing
automatically parses that file to find its scan target. You can see an
[
example of this in our Auto DevOps CI YAML
](
https://gitlab.com/gitlab-org/gitlab/blob/master/lib/gitlab/ci/templates/Jobs/Deploy.gitlab-ci.yml
)
.
Here's an example of using
`FUZZAPI_TARGET_URL`
:
```
yaml
include
:
...
...
@@ -189,7 +197,16 @@ target API to test:
FUZZAPI_HAR
:
test-api-specification.json
```
1.
Add the
`FUZZAPI_TARGET_URL`
variable and set it to the target API instance's base URL:
1.
The target API instance's base URL is also required. Provide it by using the
`FUZZAPI_TARGET_URL`
variable or an
`environment_url.txt`
file.
Adding the URL in an
`environment_url.txt`
file at your project's root is great for testing in
dynamic environments. To run API fuzzing against an app dynamically created during a GitLab CI/CD
pipeline, have the app persist its domain in an
`environment_url.txt`
file. API fuzzing
automatically parses that file to find its scan target. You can see an
[
example of this in our Auto DevOps CI YAML
](
https://gitlab.com/gitlab-org/gitlab/blob/master/lib/gitlab/ci/templates/Jobs/Deploy.gitlab-ci.yml
)
.
Here's an example of using
`FUZZAPI_TARGET_URL`
:
```
yaml
include
:
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment