Skip to content
Sign inEarly access

Navigate

Request early accessSign in
NLEN

Linking Support

Pass signed-in users on to the assistant, with what your site needs, the checklist and what a rejection reason means.

DocumentationLinking Support

An assistant on your site can address a signed-in visitor by name. For that, the server of your site passes on a short, signed JWT. Everything your developer needs is under Support, Settings, Signed-in users, in the block What your site needs.

This is one part of the Support Studio. Creating an assistant, giving it knowledge and taking over live is covered in Support Studio. Knowledge from a portal behind a login is covered in Knowledge from a portal behind a login. This page is about something else: letting the assistant know who is signed in.

What your site needs

  • Assistant id for aud, with a copy button. You may use the public key from data-assistent (dps_...) as aud instead; both work.
  • The secret (dpi_...), shown once. The screen shows whether it is active, what it starts with, when it was created and until when a previous secret still works.
  • The last check: when it last succeeded, and the last rejection reason with an explanation.

Checklist

  1. Put the secret in the server environment of your site, for example as DENKPLOEG_STEUN_GEHEIM. Never in the page, the browser code or the repo.
  2. Create a JWT with HS256, with aud and exp (at most 1 hour ahead, 10 minutes recommended).
  3. Pass it via data-identiteit on the script, or with denkploegSteunIdentificeer(jwt).
  4. Switch the assistant on under General. If it is off, the button doesn't load on your site.
  5. Test with "Do you know who I am?".

Optional in the JWT: sub, naam, email, rol, klant and velden. Don't put passwords or sensitive data in it; your team members see them in the conversation.

Prompt for your developer

The button Copy prompt for your developer puts a ready-made brief on your clipboard: assistant id, start of the key, the claims table, an example in Node.js and PHP, rules and testing. The secret itself is never in it; you hand that over separately.

When it doesn't work

A proof that doesn't check out gives no error message: the visitor is then anonymous. The screen shows the last reason and what your site should do.

ReasonWhat it meansWhat the site does
handtekeningThe signature doesn't match the secret.Sign with the current secret; restart after switching.
verlopenThe proof had already expired.Fresh proof per page view, exp 10 minutes ahead, check the clock.
audaud is not the assistant id.Use the assistant id or the dps_ key.
formaatNot a JWT of three parts.Only the JWT, without Bearer or quotes.
algoritmeNot HS256.Sign with HS256.
geen-expexp is missing.Add exp.
te-lang-geldigexp is more than 1 hour ahead.At most 1 hour, 10 minutes recommended.
nog-niet-geldigiat or nbf is in the future.Check the server's clock.
claims-te-grootThe proof or a claim is too large.Stay within the limits in the prompt.
claims-ongeldigA claim has the wrong type, or the email address is invalid.Text for the fixed claims, an object for velden.