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

If you want to secure your API, there are several better things you can do, for example:

* Make sure you have well defined Pydantic models for your request bodies and responses.
* Configure any required permissions and roles using dependencies.
* Never store plaintext passwords, only password hashes.
* Implement and use well-known cryptographic tools, like Passlib and JWT tokens, etc.

/**
 * 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

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:

<%@page pageEncoding="UTF-8" contentType="text/html; charset=UTF-8"%>
<footer role="contentinfo">
	<div class="container text-center">
		<p class="text-muted">
			<la:message key="labels.footer.copyright" />
		</p>
	</div>

    /**
     * Current page number in pagination.
     */
    private int currentPageNumber;

    /**
     * ID of the role.
     */
    public String id;

    /**
     * Name of the role.
     */
    public String name;

    /**
     * Version number of the role.
     */
    public String versionNo;

    /**
     * Clears the pager's state.
     */
    public void clear() {

comma-separated list of IAM access policy names already defined in the server. In this situation, the server prints a role ARN at startup that must be specified as a `RoleArn` API request parameter in the STS AssumeRoleWithWebIdentity API call. When using Role Policies, multiple OpenID providers and/or client applications (with unique client IDs) may be configured with independent role policies. Each configuration is assigned a unique RoleARN by the MinIO server and this is used to select the policies...

    <jsp:include page="/WEB-INF/view/common/admin/sidebar.jsp">
        <jsp:param name="menuCategoryType" value="user"/>
        <jsp:param name="menuType" value="role"/>
    </jsp:include>
    <div class="content-wrapper">
        <div class="content-header">
            <div class="container-fluid">
                <div class="row mb-2">
                    <div class="col-sm-6">

                                                        <div class="modal fade" id="confirmToAllDelete"
                                                             tabindex="-1" role="dialog">
                                                            <div class="modal-dialog">
                                                                <div class="modal-content bg-danger">

            logger.debug("Ignored SID: {} {}", type, sid);
        }
        return null;
    }

    /**
     * Creates a search role.
     * @param type The SID type.
     * @param name The account name.
     * @return The search role.
     */
    protected String createSearchRole(final int type, final String name) {
        if (fessConfig.isLdapLowercasePermissionName()) {