Skip to content
This repository was archived by the owner on Sep 30, 2020. It is now read-only.

Feature/recording readme#2

Open
SuperKmar wants to merge 7 commits intomasterfrom
feature/recording_readme
Open

Feature/recording readme#2
SuperKmar wants to merge 7 commits intomasterfrom
feature/recording_readme

Conversation

@SuperKmar
Copy link
Contributor

First commit updates readme

Second commit concerns a missed bug on saving boolean values in the pipeline configuration (as well as adding the --ip option for running docker)

@SuperKmar SuperKmar requested a review from d0nt-panic December 23, 2019 15:09
@SuperKmar SuperKmar force-pushed the feature/recording_readme branch from a3557e9 to 0750ae7 Compare December 24, 2019 14:36
README.md Outdated

The FAST plugin uses prerecorded TestRecords to run security tests as a separate build stage in your pipeline. It requires your target application to be up and running. FAST will use the same authentication as in the TestRecord. The host will be resolved via header-host unless a specific address is provided (via app_host and app_port - this option is recommended).

The FAST API TOKEN is always a required paramater for the plugin to function.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

parameter

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Resolved as outdated

README.md Outdated

Should you require automatic recording of Baselines, a recording mode is provided. This mode will allow you to send your test traffic through the FAST proxy. All requests sent this way will be recorded into a new TestRecord for later use.
For this to work, some extra paramaters need to be provided, like the port where the FAST docker container will accept incomming requests. If your application is running inside docker specifying a local docker netword and ip will also be required.
Providing a name for the docker container is not required, but will help in cleanup if the build fails outside of the plugin scope. Without this paramater, the only (automatic) way for the proxy to shut down after recording plugin is by waiting out the Inactivity_timeout

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • parameter

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Resolved as outdated

{
title: 'Allowed hosts',
field: 'allowed_hosts',
description: 'limits the hosts that will be recieving payloads (only playback mode)',

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

receiving

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Resolved as outdated

@SuperKmar SuperKmar force-pushed the feature/recording_readme branch 2 times, most recently from f07cb9b to e1ebb86 Compare December 26, 2019 11:29
@SuperKmar SuperKmar force-pushed the feature/recording_readme branch from e1ebb86 to 036cc1f Compare December 26, 2019 12:18
SuperKmar referenced this pull request in jenkinsci/wallarm-fast-plugin Mar 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants