}
```

### Usuario inactivo { #inactive-user }

Ahora prueba con un usuario inactivo, autentícate con:

Usuario: `alice`

Contraseña: `secret2`

Y trata de usar la operación `GET` con la path `/users/me`.

Obtendrás un error de "Usuario inactivo", como:

```JSON
{
  "detail": "Inactive user"
}
```

## Recapitulación { #recap }

* `externalDocs`: 外部ドキュメントを説明する `dict`。以下を含みます:
    * `description`: 外部ドキュメントの短い説明の `str`。
    * `url` (**必須**): 外部ドキュメントのURLの `str`。

### タグのメタデータの作成 { #create-metadata-for-tags }

`users` と `items` のタグを使った例で試してみましょう。

タグのメタデータを作成し、それを `openapi_tags` パラメータに渡します:

{* ../../docs_src/metadata/tutorial004_py310.py hl[3:16,18] *}

     * changes: https://mail.openjdk.org/pipermail/core-libs-dev/2013-May/thread.html#17367
     *
     * TODO(cpovirk): decide what the best long-term action here is: force users
     * to suppress (as we do now), stop testing entrySet().add() at all, make
     * entrySet().add() tests tolerant of either behavior, introduce a map
     * feature for entrySet() that supports add(), or something else
     */

1. APIs marked with the `@Beta` annotation at the class or method level
are subject to change. They can be modified in any way, or even
removed, at any time. If your code is a library itself (i.e. it is
used on the CLASSPATH of users outside your own control), you should
not use beta APIs, unless you [repackage] them. **If your
code is a library, we strongly recommend using the [Guava Beta Checker] to
ensure that you do not use any `@Beta` APIs!**

    Property<String> getSomeProperty()
}
class Example {
    Property<NestedType> getNestedProperty()
}
```

This is unnecessary because users will have trouble creating instances of `NestedType` and merging different instances of `NestedType`. It's also more awkward for users to access the properties in the nested property.

If the nested type is a managed type (Gradle can generate its implementation), you can define a nested property with:

}
```

### Неактивный пользователь { #inactive-user }

Теперь попробуйте с неактивным пользователем, аутентифицируйтесь с:

Пользователь: `alice`

Пароль: `secret2`

И попробуйте использовать операцию `GET` с путём `/users/me`.

Вы получите ошибку "Inactive user", как здесь:

```JSON
{
  "detail": "Inactive user"
}
```

## Резюме { #recap }

import org.codelibs.fess.app.pager.RolePager;
import org.codelibs.fess.mylasta.direction.FessConfig;
import org.codelibs.fess.opensearch.user.cbean.RoleCB;
import org.codelibs.fess.opensearch.user.exbhv.RoleBhv;
import org.codelibs.fess.opensearch.user.exbhv.UserBhv;
import org.codelibs.fess.opensearch.user.exentity.Role;
import org.codelibs.fess.util.ComponentUtil;
import org.dbflute.cbean.result.PagingResultBean;

        SpnegoAuthenticator authenticator = new SpnegoAuthenticator();
        assertNotNull(authenticator);

        // The security warning comments should guide users to disable this in production
        // This is a compile-time check that the code structure is correct
        assertTrue(true);
    }

    @Test
    public void test_constantsExist() {

	case "mysql", "sqlserver":
		// these dialects do not support the "returning" clause
		return
	default:
		// This user struct will leverage the existing users table, but override
		// the Name field to default to null.
		type user struct {
			gorm.Model
			Name string `gorm:"default:null"`
		}
		u1 := user{}

		if results := DB.Create(&u1); results.Error != nil {
			t.Fatalf("errors happened on create: %v", results.Error)

   *
   * @param values a series of values
   * @since 33.4.0 (but since 28.2 in the JRE flavor)
   */
  @IgnoreJRERequirement // Users will use this only if they're already using streams.
  public void addAll(DoubleStream values) {
    addAll(values.collect(StatsAccumulator::new, StatsAccumulator::add, StatsAccumulator::addAll));
  }

  /**