You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Allows to obtain the full results of a scan, messages in/out of scope and message with I/O errors.
12
+
13
+
## 1.1.1 (2017-03-09)
14
+
15
+
### Bug Fixes
16
+
- Fixed a bug that prevented the new API methods (that don't require the API key) from being used with ZAP versions <= 2.5.0.
17
+
18
+
## 1.1.0 (2017-03-09)
19
+
20
+
### Enhancements
21
+
- The `ClientApi` now allows to set the API key through the constructor, which ensures that the API key is sent whenever required. The API methods that allowed to pass the API key were deprecated in favour of using the new constructor.
22
+
- It's now possible to specify the API key in all Ant tasks.
23
+
- It's now possible to obtain the keys of the values of an `ApiResponseSet` (also, deprecated unused/unnecessary constructor and method).
24
+
- The `Alert` now exposes the alert ID, message ID and scanner ID.
-`Alert` and `AlertTask` now use `name` instead of `alert` for the name of the alert (zaproxy/zaproxy#1341), older methods were deprecated.
27
+
28
+
### Bug Fixes
29
+
-`ApiResponseSet` now has as values `ApiResponse` (zaproxy/zaproxy#3228).
30
+
31
+
### New APIs
32
+
33
+
- Context Alert Filters API, for more information refer to the help page: https://github.com/zaproxy/zap-extensions/wiki/HelpAddonsAlertFiltersAlertFilter
34
+
35
+
### Updated APIs
36
+
37
+
- AJAX Spider API
38
+
- Allows to scan a context, as a user and just a subtree.
39
+
- Selenium API
40
+
- Allows to choose which Firefox binary is used and set the path to geckodriver.
41
+
42
+
## 1.0.0 (2016-06-03)
43
+
44
+
First version as "stand alone library", it was migrated from the [zaproxy repository](https://github.com/zaproxy/zaproxy) and released to Maven Central.
Copy file name to clipboardExpand all lines: README.md
+102-1Lines changed: 102 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ can be obtained from [Maven Central](http://search.maven.org/) with following co
17
17
18
18
* GroupId: `org.zaproxy`
19
19
* ArtifactId: `zap-clientapi`
20
-
* Version: `1.0.0`
20
+
* Version: `1.2.0`
21
21
22
22
Previous releases are also available, more details can be found in [Maven Central](http://search.maven.org/#search|ga|1|org.zaproxy).
23
23
@@ -31,3 +31,104 @@ For help using OWASP ZAP API refer to:
31
31
## Issues
32
32
33
33
To report issues related to OWASP ZAP API, bugs and enhancements requests, use the [issue tracker of the main OWASP ZAP project](https://github.com/zaproxy/zaproxy/issues).
34
+
35
+
## Building
36
+
37
+
This project uses Gradle to build its libraries, for example, running:
38
+
39
+
./gradlew build
40
+
41
+
in the main directory of the project will build all the libraries. The libraries will be located in the `build/libs` directory
42
+
of each subproject.
43
+
44
+
### Installing
45
+
46
+
To install the artifacts to the local Maven repository you can run the following:
47
+
48
+
./gradlew install
49
+
50
+
The installed artifacts (`zap-clientapi`) are then available for other (local) projects to use.
51
+
52
+
## Releasing
53
+
54
+
In the following sections it will be explained the steps necessary to release a new version of the libraries. In all steps the
55
+
version to be released is referred to as `<version-to-release>`, which should be replaced with appropriate version number
56
+
(e.g. 2.1.0).
57
+
58
+
### Release Branching
59
+
60
+
The project follows the [git-flow branching model](http://nvie.com/posts/a-successful-git-branching-model/). To release a new version it needs to be created a new release branch, update the version, and tag:
0 commit comments