Auth Webhook

Webhook is an HTTP POST that is called when something happens. When specified, Auth Webhook causes Server to query an outside REST service when determining user privileges.

This page shows how to set up a auth webhook. The overall flow is as follows:

(5) response the request  (4) handle the request
     ┌─────────────────┐  ┌──┐
     │                 │  │  │   (3) response
     ▼                 │  ▼  │    - allowed
 ┌──────┐             ┌┴─────┤    - reason   ┌──────────────┐
 │Client├────────────►│Server│◄──────────────┤Outside Server│
 └──────┘ (1)request  └────┬─┘               └──────────────┘
           - token         │                      ▲
           - dockey        └──────────────────────┘
                               (2) call webhook
                                - token
                                - dockey
                                - verb: r or rw

How to implement

First, We need to pass some tokens (that identify users in the service) when creating a client:

yorkie.createClient('localhost:8080', {
  token: SOME_TOKEN,

this token will be sent to the Server on every request from the client.

And when running an Server, We can specify the Auth Webhook by the --authorization-webhook flag:

$ yorkie server --authorization-webhook=http://localhost:3000/auth-hook

The Server who receives the token calls the given webhook URL before processing the requests.

Here is an example of the webhook requests:

  "token": "SOME_TOKEN",          // token passed by the client
  "method": "PushPull",           // method: ActivateClient, DeactivateClient, AttachDocument, DetachDocument, WatchDocuments
  documentAttributes: [{
    key: "DOCUMENT_KEY",          // document key
    verb: "r"                     // 'r' or 'rw'

The outside server should respond like this:

  "allowed": true, // or false if the given token is not privileged for this document.
  "reason": "ok"   // [optional] reason for this response.

If the server receives a response with allowed: true from the outside server, it handles the request normally, otherwise it response an error with codes.Unauthenticated to the client.

Edit this page