Log Message Block

This block provides the ability to Log message during constraint chain execution. Log messages can be static or dynamic:

  • static: Static messages are logged as is without any computations.
  • dynamic: Dynamic messages are composed at run-time via expression language. (See examples below)


Specify the name for the block.


Provide a description for this block.

What message should be logged? *

Provide the information that should be logged. You can use expression language to select dynamic values at runtime. An example is as follows:

Log message: User's identity is ${headers.user_identity}.

At runtime, system will look for "user_identity" in headers and replace the value with extracted value. Ex:


headers: {
  "user_identity": "john doe",
  "user_role": "Teller"

The message that will be logged is:

User's identity is john doe.

Following global object are available at runtime:

Object Name Content Description
headers Headers Request headers. Value can be extracted as ${headers.header_name}
queryParams Query Parameters Query Parameters. Value can be extraced as ${queryParams.param_name}
authzContext Authorization Context Authorization Context that has been passed in from Resource Server. Value can be extracted as ${authzContext.param_name}
systemInfo System Information System information map that has been passed in from Resource Server. System information can contain information such as ipAddress of resource server. Value can be extracted as ${systemInfo.param_name}
messageContext Message Context Message Context is computed by AuthScope and following value as available in message context by default: scope, action, resource, pathParams. Any variables created in a constraint chain via "Create Variable" block are also available in this object. Value can be extracted as ${messageContext.param_name}

results matching ""

    No results matching ""