zitadel/docs/docs/apis/actions.md
Florian Forster 220c8e4922
docs: V2 alpha readme (#3669)
* docs: add actions dok from v1

* docs: change readme

* remove billing which will be redone

* fix search

* use readme branch to test index

* fix algolia

* fine tune

* tweak

* test

* Update netlify.toml

* Update netlify.toml

* Update docusaurus.config.js

* Update docusaurus.config.js

* Apply suggestions from code review

Co-authored-by: mffap <mpa@zitadel.com>

* tweak readme

* Apply suggestions from code review

Co-authored-by: Silvan <silvan.reusser@gmail.com>
Co-authored-by: Fabi <38692350+hifabienne@users.noreply.github.com>

* fix broken part of contrib guide

Co-authored-by: mffap <mpa@zitadel.com>
Co-authored-by: Silvan <silvan.reusser@gmail.com>
Co-authored-by: Fabi <38692350+hifabienne@users.noreply.github.com>
2022-05-20 14:20:31 +00:00

3.2 KiB

title
Actions

This page describes the options you have when writing ZITADEL actions scripts.

Language

ZITADEL interpretes the scripts as JavaScript. Make sure your scripts are ECMAScript 5.1(+) compliant. Go to the goja GitHub page for detailed reference about the underlying library features and limitations.

Actions do not have access to any libraries yet. Also, sending HTTP requests is not supported yet. We plan to add such features in the future.

Flows

Each flow type supports its own set of:

  • Triggers
  • Readable information
  • Writable information

For reading and mutating state, the runtime executes the function that has the same name as the action. The function receives the JavaScript objects ctx and api.

The object ctx provides readable information as object properties and by callable functions. The object api provides mutable properties and state mutating functions.

The script of an action called doSomething should have a function called doSomething and look something like this:

function doSomething(ctx, api){
    // read from ctx and manipulate with api
}

ZITADEL supports only the external authentication flow at the moment. More flows are coming soon.

External authentication flow triggers

  • Post authentication: A user has authenticated externally. ZITADEL retrieved and mapped the external information.
  • Pre creation: A user selected Register on the overview page after external authentication. ZITADEL did not create the user yet.
  • Post creation: A user selected Register on the overview page after external authentication. ZITADEL created the user.

External authentication flow context

  • ctx.accessToken string
    This can be an opaque token or a JWT
  • ctx.idToken string
  • ctx.getClaim(string) any
    Returns the requested claim
  • ctx.claimsJSON() object
    Returns the complete payload of the ctx.idToken

External authentication flow api

  • api.setFirstName(string)
  • api.setLastName(string)
  • api.setNickName(string)
  • api.setDisplayName(string)
  • api.setPreferredLanguage(string)
  • api.setGender(Gender)
  • api.setUsername(string)
    This function is only available for the pre creation trigger
  • api.setPreferredUsername(string)
    This function is only available for the post authentication trigger
  • api.setEmail(string)
  • api.setEmailVerified(bool)
  • api.setPhone(string)
  • api.setPhoneVerified(bool)
  • api.metadata array<Metadata>
    Push entries.
  • api.userGrants array<UserGrant>
    Push entries.
    This field is only available for the post creation trigger

External authentication flow types

  • Gender is a code number
code gender
0 unspecified
1 female
2 male
3 diverse
  • UserGrant is a JavaScript object
{
    ProjectID: string,
    ProjectGrantID: string,
    Roles: Array<string>,
}
  • Metadata is a JavaScript object with string values. The string values must be Base64 encoded

Further reading