Check for Authorization in Dynamic Collection v1.0.0 Help ​

Checks if a specific authorization exists within a dynamic collection and retrieves its details.

How can I use the Step? ​

The Step lets you verify the existence of a specific authorization in a dynamic collection and retrieve its associated details. It's useful in scenarios where you must ensure a particular authorization is available before performing actions that depend on it.

How does the Step work? ​

The Step examines a specified dynamic collection within the __authorizer_dynamic_collections folder to check for the presence of a given authorization key.

Dynamic collection settings ​

This section outlines the parameters for configuring the Step's interaction with dynamic collections:

  • Authorization source: Defines how the Step receives authorization information. You can inherit the dynamic collection name and authorization key from the previous Step or define them manually. Exception: The inheritance option doesn't work with the List Authorization in Dynamic Collection Step.
  • Dynamic collection name: Name of the dynamic collection where to check for the authorization. This name must match one of the existing dynamic collections in your key-value storage.
  • Authorization key: Specific authorization key you want to check within the dynamic collection.
  • Handle no auth separately from error: Adds an additional no auth exit for cases when the provided authorization key does not exist.

Merge field settings ​

The Step returns the result as a JSON object and stores it under the Merge field name. To learn more about Merge fields and how to work with them, see our Merge fields guide.

Output example ​

The output JSON object includes the status of the check, the authorization key, the authorization service name, and the collection name. For example:

json
{
    "status": "ok",
    "key": "kinde_basic_test_2",
    "service": "__authorization_service_Kinde",
    "collectionName": "Kinde_oauth"
}
{
    "status": "ok",
    "key": "kinde_basic_test_2",
    "service": "__authorization_service_Kinde",
    "collectionName": "Kinde_oauth"
}

Error Handling ​

By default, the Step handles errors using a separate exit. If any error occurs during the Step execution, the Flow proceeds down the error exit. For more information, see Error and timeout handling.

Reporting ​

The Step automatically generates Reporting events during its execution, allowing for real-time tracking and analysis of its performance and user interactions. To learn more, see Reporting events.

Service dependencies ​

  • sdk-api v2.17.0
  • access event-manager v2.1.0
  • oauth redirect endpoint provider v2.1.6

Release notes ​

v1.0.0

  • Initial release