Sie erweitert lediglich OAuth2, indem sie einige Dinge spezifiziert, die in OAuth2 relativ mehrdeutig sind, um zu versuchen, es interoperabler zu machen.

Beispielsweise verwendet der Google Login OpenID Connect (welches seinerseits OAuth2 verwendet).

Aber der Facebook Login unterstützt OpenID Connect nicht. Es hat seine eigene Variante von OAuth2.

### OpenID (nicht „OpenID Connect“)

It just extends OAuth2 specifying some things that are relatively ambiguous in OAuth2, to try to make it more interoperable.

For example, Google login uses OpenID Connect (which underneath uses OAuth2).

But Facebook login doesn't support OpenID Connect. It has its own flavor of OAuth2.

### OpenID (not "OpenID Connect") { #openid-not-openid-connect }

							</li>
						</c:when>
						<c:when test="${ pageLoginLink }">
							<li class="nav-item"><la:link href="/login"
									styleClass="nav-link  " role="button" aria-haspopup="true"
									aria-expanded="false">
									<em class="fa fa-fw fa-sign-in">
									<span><la:message key="labels.login" /></span>
								</la:link></li>
						</c:when>
					</c:choose>

							</li>
						</c:when>
						<c:when test="${ pageLoginLink }">
							<li class="nav-item"><la:link href="/login"
									styleClass="nav-link  " role="button" aria-haspopup="true"
									aria-expanded="false">
									<em class="fa fa-fw fa-sign-in">
									<span><la:message key="labels.login" /></span>
								</la:link></li>
						</c:when>
					</c:choose>

    }

    /**
     * Tests the ordinal values of the enum constants.
     */
    @Test
    void testEnumOrdinals() {
        // Verify the ordinal values, which can be important if they are used in logic
        assertEquals(0, ResolverType.RESOLVER_WINS.ordinal());
        assertEquals(1, ResolverType.RESOLVER_BCAST.ordinal());
        assertEquals(2, ResolverType.RESOLVER_DNS.ordinal());

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

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

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

説明文 (description) の中で Markdown を使用できることに注意してください。たとえば、「login」は太字 (**login**) で表示され、「fancy」は斜体 (_fancy_) で表示されます。

/// tip | 豆知識

使用するすべてのタグにメタデータを追加する必要はありません。

///

### 自作タグの使用

`tags` パラメーターを使用して、それぞれの *path operations* (および `APIRouter`) を異なるタグに割り当てます:

    /**
     * Retrieves a specific document by ID.
     *
     * @param id the document ID to retrieve
     * @return JSON response containing the document
     */
    // GET /api/admin/searchlist/doc/{doc_id}
    @Execute
    public JsonResponse<ApiResult> get$doc(final String id) {
        return asJson(new ApiDocResponse().doc(searchEngineClient.getDocument(fessConfig.getIndexDocumentUpdateIndex(), builder -> {

 */
package org.codelibs.fess.app.logic;

import org.codelibs.fess.mylasta.action.FessUserBean;
import org.dbflute.hook.AccessContext;
import org.dbflute.optional.OptionalThing;
import org.lastaflute.core.time.TimeManager;
import org.lastaflute.db.dbflute.accesscontext.AccessContextResource;

import jakarta.annotation.Resource;

/**
 * The logic for access context.
 */
public class AccessContextLogic {

the potential to leak sensitive information such as "Authorization" or "Cookie" headers and the
contents of request and response bodies. This data should only be logged in a controlled way or in
a non-production environment.

You can redact headers that may contain sensitive information by calling `redactHeader()`.
```java
logging.redactHeader("Authorization");

    void connectLogon_throws_propagates() throws Exception {
        // Arrange
        doThrow(new SmbException("login failed")).when(tree).connectLogon(context);

        // Act + Assert
        SmbException ex = assertThrows(SmbException.class, () -> tree.connectLogon(context));
        assertEquals("login failed", ex.getMessage());
        verify(tree).connectLogon(context);
    }

    @Test