this.updatedTime = value;
    }

    public String getUsername() {
        checkSpecifiedProperty("username");
        return convertEmptyToNull(username);
    }

    public void setUsername(String value) {
        registerModifiedProperty("username");
        this.username = value;
    }

        this.updatedTime = value;
    }

    public String getUsername() {
        checkSpecifiedProperty("username");
        return convertEmptyToNull(username);
    }

    public void setUsername(String value) {
        registerModifiedProperty("username");
        this.username = value;
    }

    public String getWebConfigId() {
        checkSpecifiedProperty("webConfigId");

                + ", protocolScheme=" + protocolScheme + ", updatedBy=" + updatedBy + ", updatedTime=" + updatedTime + ", username="
                + username + ", docMeta=" + docMeta + "]";
    }

Betrachten wir es also aus dieser vereinfachten Sicht:

* Der Benutzer gibt den `username` und das `password` im Frontend ein und drückt `Enter`.
* Das Frontend (das im Browser des Benutzers läuft) sendet diesen `username` und das `password` an eine bestimmte URL in unserer API (deklariert mit `tokenUrl="token"`).
* Die API überprüft den `username` und das `password` und antwortet mit einem „Token“ (wir haben davon noch nichts implementiert).

     *
     * @param form the create form
     * @param username the current username
     * @param currentTime the current time
     * @return optional file authentication entity
     */
    public static OptionalEntity<FileAuthentication> getEntity(final CreateForm form, final String username, final long currentTime) {
        switch (form.crudMode) {
        case CrudMode.CREATE:

     * @param form the form containing the request header data
     * @param username the username of the user performing the operation
     * @param currentTime the current timestamp
     * @return optional entity containing the request header data, or empty if creation fails
     */
    public static OptionalEntity<RequestHeader> getEntity(final CreateForm form, final String username, final long currentTime) {
        switch (form.crudMode) {

                                    <label for="username" class="col-sm-3 text-sm-right col-form-label"><la:message
                                            key="labels.webauth_username"/></label>
                                    <div class="col-sm-9">
                                        <la:errors property="username"/>
                                        <la:text styleId="username" property="username" styleClass="form-control"/>

		}
	}

	return nil
}

func (driver *ftpDriver) CheckPasswd(c *ftp.Context, username, password string) (ok bool, err error) {
	stopFn := globalFtpMetrics.log(c, username)
	defer stopFn(0, err)

	if globalIAMSys.LDAPConfig.Enabled() {
		sa, _, err := globalIAMSys.getServiceAccount(context.Background(), username)
		if err != nil && !errors.Is(err, errNoSuchServiceAccount) {
			return false, err
		}

Por ejemplo, en una de las formas en las que se puede usar la especificación OAuth2 (llamada "password flow") se requiere enviar un `username` y `password` como campos de formulario.

La <abbr title="specification">especificación</abbr> requiere que los campos se llamen exactamente `username` y `password`, y que se envíen como campos de formulario, no JSON.

The <abbr title="specification">spec</abbr> requires the fields to be exactly named `username` and `password`, and to be sent as form fields, not JSON.

With `Form` you can declare the same configurations as with `Body` (and `Query`, `Path`, `Cookie`), including validation, examples, an alias (e.g. `user-name` instead of `username`), etc.

/// info