Identity Cloud

Scripting environment

Identity Cloud supports scripts written in JavaScript.

Access Java classes

Scripts can only import Java classes on the allowlist. Identity Cloud defines an allowlist per script type.

To access Java classes in a script, use the JavaImporter:

  • Legacy

var fr = JavaImporter(

if (callbacks.isEmpty()) {
    action = fr.Action.send(
      new fr.NameCallback("Enter Your First Name"),
      new fr.NameCallback("Enter Your Last Name")
} else {
    nodeState.putShared("FirstName", callbacks.get(0).getName());
    nodeState.putShared("LastName", callbacks.get(1).getName());
    action = fr.Action.goTo("true").build();

To reduce the need to allowlist Java classes, consider migrating your scripts to use the next-generation scripting engine, which includes enhanced built-in script bindings for accessing many common script operations and the ability to include third-party software with library scripts.

Next-generation scripts

To enhance security, the next-generation scripting engine for decision node scripts doesn’t support a configurable allowlist for Java classes.

Instead, check if next-generation bindings provide the functionality you need or implement the functionality as a reusable library script.

For example, use the callbacksBuilder binding for callback functionality:

  • Next-generation

if (callbacks.isEmpty()) {
  // Request callbacks
    "First Name", "First Name");
    "Last Name", "Last Name");
} else {
  // Callbacks returned
  var firstName =
  var lastName =

  nodeState.putShared("FirstName", firstName);
  nodeState.putShared("LastName", lastName);


For information about next-generation bindings and library scripts, refer to:

Supported libraries

Identity Cloud uses the Mozilla Rhino JavaScript engine version 1.7.14 to run JavaScript. Rhino has limited support for ES6 / ES2015 (JavaScript version 1.7).

For more information, refer to Rhino ES2015 Support.

Thread pools

Identity Cloud scripting engines configure security and thread pools.

The scripting engine defines a thread pool for each script type.

Each script executes in an individual thread. The scripting engine allocates threads until it reaches a maximum of 50 threads per pool. When the scripting engine reaches the maximum number of threads, it queues scripts until a thread becomes available.

When a script has either completed or remained idle for more than 60 seconds, the script engine terminates the thread and makes it available to the pool.

Copyright © 2010-2024 ForgeRock, all rights reserved.