// in Using IAM.
	//
	// Arn is a required field
	Arn string

	// A unique identifier that contains the role ID and the role session name of
	// the role that is being assumed. The role ID is generated by AWS when the
	// role is created.
	//
	// AssumedRoleId is a required field
	AssumedRoleID string `xml:"AssumeRoleId"`
	// contains filtered or unexported fields
}

                    return "expires,start_time,end_time";
                case FessConfig.INDEX_ADMIN_REQUIRED_FIELDS:
                    return "url,title,role,boost";
                case FessConfig.INDEX_ADMIN_ARRAY_FIELDS:
                    return "alerts,roles";

                case FessConfig.INDEX_FIELD_CACHE:
                    return "cache";
                case FessConfig.INDEX_FIELD_DIGEST:

							<p><la:message key="labels.menu_user" /></p>
						</a></li></c:if>

					<c:if test="${fe:permission('admin-role-view')}">
					<li class="nav-item">
						<a href="${fe:url('/admin/role/')}" class="nav-link <c:if test="${param.menuType=='role'}">active</c:if>">
							<em class='fa fa-genderless nav-icon'>
							<p><la:message key="labels.menu_role" /></p>
						</a></li></c:if>

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.

        final String keyProp = NAME_PREFIX + id;
        doc.put(KEY_PROPERTY, keyProp);
        doc.put("url", "http://example.com/" + id);
        doc.put("boost", id);
        doc.put("role", "Rguest");
        requestBody.put("doc", doc);
        return requestBody;
    }

    @Override
    protected Map<String, Object> createSearchBody(final int size) {

    @Override
    protected String getActionRole() {
        return ROLE;
    }

    // ===================================================================================
    //

    /**
     * Displays the general settings index page.
     *
     * @return HTML response for the general settings page
     */
    @Execute
    @Secured({ ROLE, ROLE + VIEW })
    public HtmlResponse index() {
        saveToken();

        if (StringUtil.isNotBlank(forumLink)) {
            runtime.registerData("forumLink", forumLink);
        }
    }

    /**
     * Get the action role.
     * @return The action role.
     */
    protected abstract String getActionRole();

    /**
     * Writes data to the specified file path.
     *
     * @param path the file path to write to

            "registeredAddress", null, false, false, false, "keyword", 0, 0, null, null, false, null, null, null, null, null, false);
    protected final ColumnInfo _columnRoles = cci("roles", "roles", null, null, String[].class, "roles", null, false, false, false,
            "keyword", 0, 0, null, null, false, null, null, null, null, null, false);

      },
      "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