Retrieve Attribute from User Store

Overview

The API Gateway user store contains user profiles, including attributes relating to each user. After a user has successfully authenticated to the API Gateway, the Retrieve From User Store filter can retrieve attributes belonging to that user from the user store.

General Configuration

Configure the following field:

Name:

Enter an appropriate name for this filter.

Database

Configure the following fields on the Database tab:

User ID:

Select or enter the name of the message attribute that contains the name of the user to look up in the user store. For example, if the user name is stored as admin, you must select the message attribute containing the value admin. The API Gateway then looks up the user the user store using this name.

Attributes:

Enter the list of attributes that the API Gateway should retrieve if it successfully looks up the user identified by the message attribute specified in the User ID field. You can add attributes by selecting the Add button. Similarly, you can edit and remove existing attributes by selecting the Edit and Remove buttons.

Advanced

Configure the following fields on the Advanced tab:

Enable legacy attribute naming for retrieved attributes:

Specifies whether to enable legacy naming of retrieved message attributes (unselected by default). Prior to version 7.1, retrieved attributes were stored in message attributes in the following format:

user.<retrieved_attribute_name>

For example, ${user.email}, ${user.role}, and so on. If the retrieved attribute was multi-valued, you would access the values using ${user.email.1} or ${user.email.2}, and so on. In version 7.1 and later, by default, you can query for multi-valued retrieved attributes using an array syntax (for example, ${user.email[0]} or ${user.email[1]}, and so on). Select this setting if you wish to use the legacy format for attribute naming instead.

Prefix for message attribute names:

You can specify an optional prefix for message attribute names. The default prefix is user..

Fail on empty result set:

Specify whether this filter fails if the result set is empty. This setting is not selected by default.