* The frontend stores that token temporarily somewhere.
* The user clicks in the frontend to go to another section of the frontend web app.
* The frontend needs to fetch some more data from the API.
    * But it needs authentication for that specific endpoint.
    * So, to authenticate with our API, it sends a header `Authorization` with a value of `Bearer ` plus the token.

So, to renew the certificates, the renewal program needs to **prove** to the authority (Let's Encrypt) that it indeed **"owns" and controls that domain**.

To do that, and to accommodate different application needs, there are several ways it can do it. Some popular ways are:

* **Modify some DNS records**.

Each section gradually builds on the previous ones, but it's structured to separate topics, so that you can go directly to any specific one to solve your specific API needs.

It is also built to work as a future reference so you can come back and see exactly what you need.

## Run the code { #run-the-code }

        uses: eps1lon/actions-label-merge-conflict@v3
        with:
          dirtyLabel: "conflicts"
          repoToken: "${{ secrets.GITHUB_TOKEN }}"

`swagger_ui_parameters` receives a dictionary with the configurations passed to Swagger UI directly.

FastAPI converts the configurations to **JSON** to make them compatible with JavaScript, as that's what Swagger UI needs.

## Disable Syntax Highlighting { #disable-syntax-highlighting }

For example, you could disable syntax highlighting in Swagger UI.

Without changing the settings, syntax highlighting is enabled by default:

        // The process method needs actual ThumbnailQueueBhv and other components
        assertTrue(true);
    }

    // Test process with unavailable generator
    public void test_process_unavailableGenerator() {
        // Skip this test as it requires container components
        // The process method needs actual ThumbnailQueueBhv and other components
        assertTrue(true);
    }

The `name="static"` gives it a name that can be used internally by **FastAPI**.

All these parameters can be different than "`static`", adjust them with the needs and specific details of your own application.

## More info { #more-info }

Swagger UI will handle it behind the scenes for you, but it needs this "redirect" helper.

///

### Create a *path operation* to test it { #create-a-path-operation-to-test-it }

Now, to be able to test that everything works, create a *path operation*:

    public void test_isTarget() {
        // Test isTarget method
        generator = new TestThumbnailGenerator();
        Map<String, Object> docMap = new HashMap<>();

        // Note: isTarget requires FessConfig which needs container
        // We can only verify the method handles missing container gracefully
        try {
            generator.isTarget(docMap);
        } catch (IllegalStateException e) {

    }

    public void test_isTarget() {
        // Initialize without container
        emptyGenerator = new EmptyGenerator();

        // Note: isTarget method requires FessConfig from ComponentUtil
        // which needs container initialization.
        // We can only test that the method can be called without crashing
        // when proper conditions are not met.

        Map<String, Object> docMap = new HashMap<>();