summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJeff Fearn <jfearn@redhat.com>2021-09-21 08:31:06 +1000
committerJeff Fearn <jfearn@redhat.com>2021-09-21 08:31:06 +1000
commit9a1db0ec2150c0974414135436dce86d7f143106 (patch)
tree461f0dc3dbf126b03b6cb8a857cb0485f2a37160 /Bugzilla/WebService.pm
parentBug 2004788 - Slow load on create bug page (diff)
downloadbugzilla-9a1db0ec2150c0974414135436dce86d7f143106.tar.gz
bugzilla-9a1db0ec2150c0974414135436dce86d7f143106.tar.bz2
bugzilla-9a1db0ec2150c0974414135436dce86d7f143106.zip
Bug 2005448 - Authentication typo in docs for the API_KEY header
Fix typo. Change-Id: I650cd70e3515cc346dafc4eea02f7a33b86d1127
Diffstat (limited to 'Bugzilla/WebService.pm')
-rw-r--r--Bugzilla/WebService.pm4
1 files changed, 2 insertions, 2 deletions
diff --git a/Bugzilla/WebService.pm b/Bugzilla/WebService.pm
index f163d3741..527656c1e 100644
--- a/Bugzilla/WebService.pm
+++ b/Bugzilla/WebService.pm
@@ -173,8 +173,8 @@ Some methods do not require you to authenticate. An example of this is Bug.get.
However, authenticating yourself allows you to see non public information. For
example, a bug that is not publicly visible.
-The supported way to authenticate in Red Hat Bugzilla is to use the Authentication
-header with an API Key. C<Authentication: Bearer YOURAPIKEY>. Using this approach
+The supported way to authenticate in Red Hat Bugzilla is to use the Authorization
+header with an API Key. C<Authorization: Bearer YOURAPIKEY>. Using this approach
you do not login, you simply provide this header with every API call.
You can set up API keys by using the 'API Key' tab in the Preferences pages. It is