Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Fill the form with the desired Webhook name, the HTTP Method(s) that will be used to trigger this webhook, the path to the desired script to be invoked, and weather or not the invocation should be Synchronous or notparamenters:

  • Name - the name of the webhook. This will be used as an identificator for the webhook configuration.
  • Methods - the HTTP method (or methods) to bind the webhook to.
  • Scrip - the SIL Script that will run when calling this webhook.
  • Synchronized - the sync/async configuration for the webhook.


Note
titleNOTE

The difference between synchronous and asynchronous is that the asynchronous Webhook SIL call can't return any results or custom HTTP codes to the caller.

This happens because the SIL script run task is added to a list of future tasks to be run, and the HTTP call ends.

With the synchronous option, the call will block until the SIL script run is completed, and the results will be returned to the caller.

Image Removed

Parameters:

  • Directory - the directory type. Only MS Active Directory is supported at the moment. If you have other LDAP type, ask for support.
  • Name - the LDAP configuration name, unique.
  • Base DN - the base DN, used as a root for that LDAP.
  • User / Password - the LDAP user and the password (it is not usually a single word, but a string like shown above).

There are also two optional parameters:

  • Connection time-out, self explanatory
  • Use cache - if checked, it will cache the records. Use it for better performance, but it may not reflect exactly what's in the LDAP database.

Click the Test button to test the configuration validity. Any errors are reported back into the page dialog, allowing you to adjust your configuration until the connection is established successfully.

Once added, the LDAP configurations can be edited, removed and tested from the same page:

Image Removed


Changes are visible After saving the configuration, a new entry like the following one will show up:

Image Added


The URI column in the table will help you run your newly created wekbook. For example if your Jira installation instance is located at http://localhost, you can run the webhook using the address http://localhost/rest/keplerrominfo/refapp/latest/webhooks/mysilwebhook/run , with the selected HTTP method(s).

The webhook configured in the example image can be accessed using the HTTP methods GET and POST.

Changes are visible immediately and the webhook is immediately.


Webhooks Authentication

...