docs: combine api keys and authentication pages

SECURITY.md

@@ -59,4 +59,4 @@ Setting `LANGFLOW_SKIP_AUTH_AUTO_LOGIN=true` and `LANGFLOW_AUTO_LOGIN=true` skip
 
 `LANGFLOW_SKIP_AUTH_AUTO_LOGIN=true` is the default behavior, so users do not need to change existing workflows in 1.5. To update your workflows to require authentication, set `LANGFLOW_SKIP_AUTH_AUTO_LOGIN=false`.
 
-For more information, see [Authentication](https://docs.langflow.org/configuration-authentication).
+For more information, see [API keys and authentication](https://docs.langflow.org/api-keys-and-authentication).

docs/docs/API-Reference/api-reference-api-examples.mdx

@@ -63,7 +63,7 @@ In Langflow versions 1.5 and later, most API endpoints require a Langflow API ke
 The only exceptions are the MCP endpoints `/v1/mcp`, `/v1/mcp-projects`, and `/v2/mcp`, which never require authentication.
 
 To authenticate a Langflow API request, provide a Langflow API key in either an `x-api-key` header or query parameter.
-For more information, see [API keys](/configuration-api-keys).
+For more information, see [API keys](/api-keys-and-authentication).
 
 As with any API, follow industry best practices for storing and referencing sensitive credentials.
 For example, you can [set environment variables](#set-environment-variables) for your API keys, and then reference those environment variables in your API requests.
@@ -117,7 +117,7 @@ curl --request POST \
 }'
 ```
 
-Commonly used values in Langflow API requests include your [Langflow server URL](#base-url), [Langflow API keys](/configuration-api-keys), flow IDs, and [project IDs](/api-projects#read-projects).
+Commonly used values in Langflow API requests include your [Langflow server URL](#base-url), [Langflow API keys](/api-keys-and-authentication), flow IDs, and [project IDs](/api-projects#read-projects).
 
 You can retrieve flow IDs from the [**API access** pane](/concepts-publish#api-access), in a flow's URL, and with [`GET /flows`](/api-flows#read-flows).
 

docs/docs/Agents/agents.mdx

@@ -115,7 +115,7 @@ For example, to use the default OpenAI model, you must provide a valid OpenAI AP
 
 You can enter the key directly, but it is recommended that you follow industry best practices for storing and referencing API keys.
 For example, you can use a <Icon name="Globe" aria-hidden="true"/> [global variable](/configuration-global-variables) or [environment variables](/environment-variables).
-For more information, see [Add component API keys to Langflow](/configuration-api-keys#add-component-api-keys-to-langflow).
+For more information, see [Add component API keys to Langflow](/api-keys-and-authentication#add-component-api-keys-to-langflow).
 
 If you select **Custom** as the model provider, authentication is handled in the incoming **Language Model** component.
 

docs/docs/Concepts/concepts-file-management.mdx

@@ -18,7 +18,7 @@ You can also manage all files that have been uploaded to your Langflow server.
 
 1. Navigate to Langflow file management:
 
-    * In the Langflow UI, on the [**Projects** page](#projects) page, click **My Files** below the list of projects.
+    * In the Langflow UI, on the [**Projects** page](/concepts-flows#projects) page, click **My Files** below the list of projects.
     * From a browser, navigate to your Langflow server's `/files` endpoint, such as `http://localhost:7860/files`. Modify the base URL as needed for your Langflow server.
     * For programmatic file management, use the [Langflow API files endpoints](/api-files). However, the following steps assume you're using the file management UI.
 

docs/docs/Concepts/concepts-overview.mdx

@@ -22,7 +22,7 @@ This is where you add [components](/concepts-components), configure them, and at
 
 ![Empty Langflow workspace](/img/workspace.png)
 
-From the **Workspace**, you can also access the [**Playground**](#playground), [**Share** menu](#share-menu), and [**Logs**](/concepts-flows#flow-logs).
+From the **Workspace**, you can also access the [**Playground**](#playground), [**Share** menu](#share-menu), and [**Logs**](/concepts-flows#flow-storage-and-logs).
 
 ### Workspace gestures and interactions
 
@@ -74,4 +74,4 @@ The **Share** menu provides the following options for integrating your flow into
 
 * [Manage files in Langflow](/concepts-file-management)
 * [Global variables](/configuration-global-variables)
-* [Langflow API keys](configuration-api-keys)
+* [Langflow API keys](/api-keys-and-authentication)

docs/docs/Concepts/concepts-publish.mdx

@@ -61,7 +61,7 @@ For this script to work, you must set a `LANGFLOW_API_KEY` variable in the termi
 
 Alternatively, you can edit the code snippet to include an `x-api-key` header and ensure that the request can authenticate to the Langflow API.
 
-For more information, see [API keys](/configuration-api-keys) and [Get started with the Langflow API](/api-reference-api-examples)
+For more information, see [API keys](/api-keys-and-authentication) and [Get started with the Langflow API](/api-reference-api-examples)
 
 ### Input Schema (tweaks) {#input-schema}
 
@@ -357,7 +357,7 @@ To use the embedded chat widget in your HTML, the `langflow-chat` web component
 
 * `host_url`: Your Langflow server URL. Must be `HTTPS`. Don't include a trailing slash (`/`).
 * `flow_id`: The ID of the flow you want to embed.
-* `api_key`: A [Langflow API key](/configuration-api-keys).
+* `api_key`: A [Langflow API key](/api-keys-and-authentication).
 This prop is recommended to ensure the widget has permission to run the flow.
 
 The minimum inputs are automatically populated in the [**Embed into site** code snippet](#get-a-langflow-chat-snippet) that is generated by Langflow.

docs/docs/Concepts/mcp-server.mdx

@@ -142,7 +142,7 @@ For example:
     If you have [deployed a public Langflow server](/deployment-public-server), the address is automatically included.
 
     :::important
-    If your Langflow server [requires authentication](/configuration-authentication) ([`LANGFLOW_AUTO_LOGIN`](/environment-variables#LANGFLOW_AUTO_LOGIN) is set to `false`), you must include your Langflow API key in the configuration.
+    If your Langflow server [requires authentication](/api-keys-and-authentication) ([`LANGFLOW_AUTO_LOGIN`](/environment-variables#LANGFLOW_AUTO_LOGIN) is set to `false`), you must include your Langflow API key in the configuration.
     For more information, see [MCP server authentication and environment variables](#authentication).
     :::
 
@@ -158,7 +158,7 @@ For more information, see the [Cursor's MCP documentation](https://docs.cursor.c
 
 ### MCP server authentication and environment variables {#authentication}
 
-If your Langflow server [requires authentication](/configuration-authentication) ([`LANGFLOW_AUTO_LOGIN`](/environment-variables#LANGFLOW_AUTO_LOGIN) is set to `false`), then you must supply a [Langflow API key](/configuration-api-keys) in your MCP client configuration.
+If your Langflow server [requires authentication](/api-keys-and-authentication) ([`LANGFLOW_AUTO_LOGIN`](/environment-variables#LANGFLOW_AUTO_LOGIN) is set to `false`), then you must supply a [Langflow API key](/api-keys-and-authentication) in your MCP client configuration.
 When this is the case, the code template in your project's **MCP Server** tab automatically includes the `--header` and `x-api-key` arguments:
 
 ```json