@cryptotaxi247 / netdata-1 / commits / 3b1a7d582

highlight Challenge Secret title to be more visible (#16882)

Juan Cañete committed Jan 31, 2024 at 11:43 UTC 3b1a7d582bf77cbd093342128b28c1d8145f790c
1 file changed +2 -2
integrations/cloud-notifications/metadata.yaml
+2 -2
@@ -676,9 +676,9 @@
676
677 In bearer token authentication, the client sends a request with an Authorization header that includes a bearer token. The server then uses this token to authenticate the client. Bearer tokens are typically generated by an authentication service, and are passed to the client after a successful authentication. If this method is selected, the user can set the token to be used for connecting to the destination service.
678
679 - ###### Challenge secret
679 + ##### Challenge secret
680
681 - To validate that you has ownership of the web application that will receive the webhook events, we are using a challenge response check mechanism.
681 + To validate that you have ownership of the web application that will receive the webhook events, we are using a challenge response check mechanism.
682
683 This mechanism works as follows:
684