+
+ With 9.0.0 dependency-check has moved from using the NVD data-feed to the NVD API.
+ Users of dependency-check are highly encouraged to obtain an NVD API Key;
+ see https://nvd.nist.gov/developers/request-an-api-key
+ Without an NVD API Key dependency-check's updates will be extremely slow.
+
+
+ The NVD API Key, CI, and Rate Limiting
+ The NVD API has enforced rate limits. If you are using a single API KEY and multiple builds occur you could hit the rate limit and receive 403 errors.
+ In a CI environment one must use a caching strategy or use a set API KEY to use for different jobs.
+
+
\ No newline at end of file
diff --git a/src/main/resources/org/jenkinsci/plugins/DependencyCheck/Messages.properties b/src/main/resources/org/jenkinsci/plugins/DependencyCheck/Messages.properties
index 745d2d02..2bd566b0 100755
--- a/src/main/resources/org/jenkinsci/plugins/DependencyCheck/Messages.properties
+++ b/src/main/resources/org/jenkinsci/plugins/DependencyCheck/Messages.properties
@@ -28,6 +28,8 @@ Builder.noExecutableFound=Couldn\u2019t find any executable in "{0}"
Builder.Skip=Skipping Dependency-Check analysis
Builder.noInstallationFound=No installation {0} found. Please define one in manager Jenkins.
Builder.nodeOffline=Cannot get installation for node, since it is not online
+Builder.DescriptorImpl.emptyCredentialsId=Credentials is required
+Builder.DescriptorImpl.invalidCredentialsId=Current credentials does not exists
Platform.unknown=Unknown OS name: {0}
SystemTools.nodeNotAvailable=Node could be offline or there are no executor defined for Node {0}