## Instalar `PyJWT` { #install-pyjwt }

Nós precisamos instalar o `PyJWT` para criar e verificar os tokens JWT em Python.

Certifique-se de criar um [ambiente virtual](../../virtual-environments.md){.internal-link target=_blank}, ativá-lo e então instalar o `pyjwt`:

<div class="termy">

```console
$ pip install pyjwt

import jcifs.Credentials;

@ExtendWith(MockitoExtension.class)
class CredentialsInternalTest {

    @Mock
    CIFSContext mockContext;

    /**
     * Simple in-test implementation of CredentialsInternal to exercise the API surface.
     * It validates inputs, records calls, and delegates some behavior to collaborators
     * so we can verify interactions.
     */
    static class TestCredentials implements CredentialsInternal {

            <div class="container-fluid">
                <div class="row mb-2">
                    <div class="col-sm-6">
                        <h1>
                            <la:message key="labels.webauth_title_details"/>
                        </h1>
                    </div>
                    <div class="col-sm-6">
                        <jsp:include page="/WEB-INF/view/common/admin/crud/breadcrumb.jsp"></jsp:include>

/**
 * Exception thrown when a {@link Constructor} cannot be found.
 *
 * @author higa
 */
public class ConstructorNotFoundRuntimeException extends ClRuntimeException {

    private static final long serialVersionUID = 8584662068396978822L;

    /**
     * The target class.
     */
    private final Class<?> targetClass;

    /**
     * The method arguments.
     */
    private final Object[] methodArgs;

import org.mockito.MockedStatic;
import org.mockito.Mockito;
import org.mockito.junit.jupiter.MockitoExtension;

import jcifs.pac.PACDecodingException;

/**
 * Unit tests for the KerberosTicket class.
 */
@ExtendWith(MockitoExtension.class)
class KerberosTicketTest {

    @Mock
    private KerberosKey kerberosKey;

    private KerberosKey[] keys;

    private static final String SERVER_REALM = "EXAMPLE.COM";

@SuppressWarnings("JUnit4ClassUsedInJUnit3")
public class MultisetRemoveTester<E> extends AbstractMultisetTester<E> {
  @CollectionFeature.Require(SUPPORTS_REMOVE)
  public void testRemoveNegative() {
    assertThrows(IllegalArgumentException.class, () -> getMultiset().remove(e0(), -1));
    expectUnchanged();
  }

  @CollectionFeature.Require(absent = SUPPORTS_REMOVE)

 * Tests icon rendering with different terminal charsets and fallback behavior.
 */
@DisplayName("ConsoleIcon")
class ConsoleIconTest {

    @Test
    @DisplayName("should return Unicode icons when terminal supports UTF-8")
    void shouldReturnUnicodeWhenTerminalSupportsUtf8() {
        Terminal mockTerminal = mock(Terminal.class);
        when(mockTerminal.encoding()).thenReturn(StandardCharsets.UTF_8);

@SuppressWarnings("JUnit4ClassUsedInJUnit3")
public class MultisetRemoveTester<E> extends AbstractMultisetTester<E> {
  @CollectionFeature.Require(SUPPORTS_REMOVE)
  public void testRemoveNegative() {
    assertThrows(IllegalArgumentException.class, () -> getMultiset().remove(e0(), -1));
    expectUnchanged();
  }

  @CollectionFeature.Require(absent = SUPPORTS_REMOVE)

            return redirect(ErrorAction.class);
        }
        final String url = DocumentUtil.getValue(doc, fessConfig.getIndexFieldUrl(), String.class);
        if (url == null) {
            saveError(messages -> messages.addErrorsDocumentNotFound(GLOBAL, form.docId));
            return redirect(ErrorAction.class);
        }

        if (fessConfig.isSearchLog()) {

///

/// info

Unless you specify a different media type explicitly in your `responses` parameter, FastAPI will assume the response has the same media type as the main response class (default `application/json`).

But if you have specified a custom response class with `None` as its media type, FastAPI will use `application/json` for any additional response that has an associated model.

///