OAuth2 specifies that when using the "password flow" (that we are using) the client/user must send a `username` and `password` fields as form data.

And the spec says that the fields have to be named like that. So `user-name` or `email` wouldn't work.

But don't worry, you can show it as you wish to your final users in the frontend.

And your database models can use any other names you want.

Please use [Google Bug Hunters reporting form](https://g.co/vulnz) to report
security vulnerabilities. Please include the following information along with
your report:

  - A descriptive title
  - Your name and affiliation (if any).
  - A description of the technical details of the vulnerabilities.
  - A minimal example of the vulnerability. It is very important to let us know

     * @param config
     *            the configuration to use
     */
    public NetShareEnum(final Configuration config) {
        super(config, SMB_COM_TRANSACTION, NET_SHARE_ENUM);
        this.name = "\\PIPE\\LANMAN";
        this.maxParameterCount = 8;

        // maxDataCount = 4096; why was this set?
        this.maxSetupCount = (byte) 0x00;
        this.setupCount = 0;
        this.timeout = 5000;
    }

 * DFS referral information for redirecting clients to distributed file system targets.
 */
public class Trans2GetDfsReferralResponse extends SmbComTransactionResponse {

    /**
     * Indicates that the referral contains a name list.
     */
    public static final int FLAGS_NAME_LIST_REFERRAL = 0x0002;
    /**
     * Indicates a target set boundary in the referral response.
     */
    public static final int FLAGS_TARGET_SET_BOUNDARY = 0x0004;

import jcifs.internal.util.SMBUtil;

/**
 * SMB2 Lease V2 Create Context Response
 *
 * MS-SMB2 2.2.14.2.11
 */
public class LeaseV2CreateContextResponse implements CreateContextResponse {

    /**
     * Context name for lease V2 response
     */
    public static final String CONTEXT_NAME = "RqL2";

    private static final byte[] CONTEXT_NAME_BYTES = CONTEXT_NAME.getBytes();

    private Smb2LeaseKey leaseKey;

        void normalArray(int idx) {
            byte[] arr = new byte[12];
            assertEquals(0, response.readBytesWireFormat(arr, idx));
        }
    }

    @Test
    @DisplayName("toString contains class name and delegates to superclass")
    void toStringMatches() {
        String s = response.toString();
        assertNotNull(s);
        assertTrue(s.startsWith("SmbComSetInformationResponse["));

# ==============================================================================
# Sourcing this enables Bazel remote cache (public, read-only)
# The cache configs are different for MacOS and Linux
if [[ $(uname -s) == "Darwin" ]]; then
  TFCI_BAZEL_COMMON_ARGS="$TFCI_BAZEL_COMMON_ARGS --config tf_public_macos_cache"
else
  TFCI_BAZEL_COMMON_ARGS="$TFCI_BAZEL_COMMON_ARGS --config tf_public_cache"

これは **FastAPI** が以下のようなボディを期待することを意味します:

```JSON
{
    "name": "Foo",
    "description": "The pretender",
    "price": 42.0,
    "tax": 3.2,
    "tags": ["rock", "metal", "bar"],
    "image": {
        "url": "http://example.com/baz.jpg",
        "name": "The Foo live"
    }
}
```

繰り返しになりますが、**FastAPI** を使用して、その宣言を行うだけで以下のような恩恵を受けられます:

     */
    protected void setupListCondition(final LabelTypeCB cb, final LabelTypePager labelTypePager) {
        if (StringUtil.isNotBlank(labelTypePager.name)) {
            cb.query().setName_Wildcard(wrapQuery(labelTypePager.name));
        }
        if (StringUtil.isNotBlank(labelTypePager.value)) {
            cb.query().setValue_Wildcard(wrapQuery(labelTypePager.value));
        }

<div class="wrapper">
    <jsp:include page="/WEB-INF/view/common/admin/header.jsp"></jsp:include>
    <jsp:include page="/WEB-INF/view/common/admin/sidebar.jsp">
        <jsp:param name="menuCategoryType" value="system"/>
        <jsp:param name="menuType" value="dict"/>
    </jsp:include>
    <div class="content-wrapper">
        <div class="content-header">
            <div class="container-fluid">