the NOTICE text from the Work, provided that such additional attribution 
notices cannot be construed as modifying the License.

You may add Your own copyright statement to Your modifications and may 
provide additional or different license terms and conditions for use, 
reproduction, or distribution of Your modifications, or for any such 
Derivative Works as a whole, provided Your use, reproduction, and 

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the

 * recognized public suffix; see {@link InternetDomainName#isPublicSuffix()} for details.
 *
 * <p>Note that no network lookups are performed by any {@code HostSpecifier} methods. No attempt is
 * made to verify that a provided specifier corresponds to a real or accessible host. Only syntactic
 * and pattern-based checks are performed.
 *
 * <p>If you know that a given string represents a numeric IP address, use {@link InetAddresses} to

   *
   * QUIC is not natively supported by OkHttp, but provided to allow a theoretical interceptor that
   * provides support.
   */
  QUIC("quic"),

  /**
   * HTTP/3 is the third and upcoming major version of the Hypertext Transfer Protocol used to
   * exchange information. HTTP/3 runs over QUIC, which is published as RFC 9000.
   *
   * HTTP/3 is not natively supported by OkHttp, but provided to allow a theoretical interceptor

        return asHtml(path_AdminRelatedcontent_AdminRelatedcontentJsp).renderWith(data -> {
            searchPaging(data, form);
        });
    }

    /**
     * Searches for related content items based on the provided search criteria.
     *
     * @param form the search form containing search criteria
     * @return HTML response with filtered related content results
     */
    @Execute
    @Secured({ ROLE, ROLE + VIEW })

        infoMap.put(key, value);
    }

    /**
     * Updates crawling information parameters for the specified session.
     * Sets the name and expiration time based on the provided parameters.
     *
     * @param sessionId the session ID to update
     * @param name the name to set for the crawling session (uses system name if blank)

      result |= (input[offset + i] & 0xFFL) << (i * 8);
    }
    return result;
  }

  /**
   * Store 8 bytes into the provided array at the indicated offset, using the value provided.
   *
   * @param sink the output byte array
   * @param offset the offset into the array at which to start writing
   * @param value the value to write
   */

Those details are implementation specific.

For OAuth2 they are just strings.

///

## Code to get the `username` and `password` { #code-to-get-the-username-and-password }

Now let's use the utilities provided by **FastAPI** to handle this.

### `OAuth2PasswordRequestForm` { #oauth2passwordrequestform }

First, import `OAuth2PasswordRequestForm`, and use it as a dependency with `Depends` in the *path operation* for `/token`:

Description: Enterprise Search Server: Fess