String[] fields = new String[] { "content" };
        String[] tags = new String[] { "tag1" };
        String[] roles = new String[] { SuggestConstants.DEFAULT_ROLE };

        SuggestIndexResponse response = suggester.indexer().indexFromSearchWord(searchWord, fields, tags, roles, 1, null);

        assertNotNull(response);
        assertEquals(1, response.getNumberOfInputDocs());

	errRoleArnMissingLegacy             = Errorf("Missing required parameter `Role` in ReplicationConfiguration")
	errDestinationArnMissing            = Errorf("Missing required parameter `Destination` in Replication rule")
	errInvalidSourceSelectionCriteria   = Errorf("Invalid ReplicaModification status")
	errRoleArnPresentForMultipleTargets = Errorf("`Role` should be empty in ReplicationConfiguration for multiple targets")
)

      },
      "gidNumber" : {
        "type" : "long"
      },
      "homeDirectory" : {
        "type" : "keyword"
      },
      "groups": {
        "type": "keyword"
      },
      "roles": {
        "type": "keyword"
      }
    }

/**
 * This realizes the metadata source via the default hint to provide backward-compat with Maven 2.x whose Plexus version
 * registered component descriptors twice: once keyed by role+roleHint and once keyed by role only. This effectively
 * made the metadata source available with its original role hint ("maven") as well as the default hint.
 *
 */
@Named
@Singleton
@Deprecated
public class DefaultMetadataSource extends MavenMetadataSource {
    @Inject

     * For admin actions, verifies that the user has appropriate admin roles or
     * meets the secured annotation requirements.
     *
     * @param resource the login handling resource to check permission for
     * @throws LoginRequiredException if login is required
     * @throws UserRoleLoginException if the user doesn't have required roles
     */
    @Override

After configuring the plugin, use the generated Role ARN with `AssumeRoleWithCustomToken` to get temporary credentials to access object storage.

## API Request

To make an STS API request with this method, send a POST request to the MinIO endpoint with following query parameters:

    /** The key of the message: Query */
    public static final String LABELS_Q = "{labels.q}";

    /** The key of the message: Roles */
    public static final String LABELS_ROLES = "{labels.roles}";

    /** The key of the message: Suggest Search Log */
    public static final String LABELS_SUGGEST_SEARCH_LOG = "{labels.suggestSearchLog}";

labels.oic_base_url=Base URL
labels.oic_default_groups=Default Groups
labels.oic_default_roles=Default Roles
labels.general_menu_saml=SAML
labels.saml_sp_base_url=SP Base URL
labels.saml_attribute_group_name=Group Attribute Name
labels.saml_attribute_role_name=Role Attribute Name
labels.saml_default_groups=Default Groups
labels.saml_default_roles=Default Roles
labels.general_menu_spnego=SPNEGO
labels.spnego_krb5_conf=Krb5 Config

`MINIO_IDENTITY_PLUGIN_ROLE_POLICY` is a required parameter and can be list of comma separated policy names.

On setting up the plugin, the MinIO server prints the Role ARN to its log. The Role ARN is generated by default based on the given plugin URL. To avoid this and use a configurable value set a unique role ID via `MINIO_IDENTITY_PLUGIN_ROLE_ID`.

## REST API call to plugin

            return container.lookup(role, roleHint);
        } finally {
            Thread.currentThread().setContextClassLoader(oldClassLoader);
        }
    }

    @Override
    public Map<String, Object> getPluginComponents(Plugin plugin, String role)
            throws ComponentLookupException, PluginManagerException {