fixed library e2e

Author: jrobertboos

docker-compose-library.yaml

@@ -38,6 +38,8 @@ services:
       - ./run.yaml:/app-root/run.yaml:Z
       - ${GCP_KEYS_PATH:-./tmp/.gcp-keys-dummy}:/opt/app-root/.gcp-keys:ro
       - ./tests/e2e/rag:/opt/app-root/src/.llama/storage/rag:Z
+      - ./tests/e2e/secrets/mcp-token:/tmp/mcp-token:ro
+      - ./tests/e2e/secrets/invalid-mcp-token:/tmp/invalid-mcp-token:ro
     environment:
       # LLM Provider API Keys
       - BRAVE_SEARCH_API_KEY=${BRAVE_SEARCH_API_KEY:-}

docker-compose.yaml

@@ -81,8 +81,8 @@ services:
       - "8080:8080"
     volumes:
       - ./lightspeed-stack.yaml:/app-root/lightspeed-stack.yaml:z
-      - ./tests/e2e/secrets/mcp-token:/tmp/mcp-secret-token:ro
-      - ./tests/e2e/secrets/invalid-mcp-token:/tmp/invalid-mcp-secret-token:ro
+      - ./tests/e2e/secrets/mcp-token:/tmp/mcp-token:ro
+      - ./tests/e2e/secrets/invalid-mcp-token:/tmp/invalid-mcp-token:ro
     environment:
       - OPENAI_API_KEY=${OPENAI_API_KEY}
       # Azure Entra ID credentials (AZURE_API_KEY is obtained dynamically)

tests/e2e/configuration/library-mode/lightspeed-stack-invalid-mcp-file-auth.yaml

@@ -21,4 +21,4 @@ mcp_servers:
   - name: "mcp-file"
     url: "http://mock-mcp:3001"
     authorization_headers:
-      Authorization: "/tmp/invalid-mcp-secret-token"
+      Authorization: "/tmp/invalid-mcp-token"

tests/e2e/configuration/library-mode/lightspeed-stack-mcp-file-auth.yaml

@@ -21,4 +21,4 @@ mcp_servers:
   - name: "mcp-file"
     url: "http://mock-mcp:3001"
     authorization_headers:
-      Authorization: "/tmp/mcp-secret-token"
+      Authorization: "/tmp/mcp-token"

tests/e2e/configuration/library-mode/lightspeed-stack-mcp.yaml

@@ -29,7 +29,7 @@ mcp_servers:
   - name: "mcp-file"
     url: "http://mock-mcp:3001"
     authorization_headers:
-      Authorization: "/tmp/mcp-secret-token"
+      Authorization: "/tmp/mcp-token"
   - name: "mcp-client"
     url: "http://mock-mcp:3001"
     authorization_headers:

tests/e2e/configuration/server-mode/lightspeed-stack-invalid-mcp-file-auth.yaml

@@ -22,4 +22,4 @@ mcp_servers:
   - name: "mcp-file"
     url: "http://mock-mcp:3001"
     authorization_headers:
-      Authorization: "/tmp/invalid-mcp-secret-token"
+      Authorization: "/tmp/invalid-mcp-token"

tests/e2e/configuration/server-mode/lightspeed-stack-mcp-file-auth.yaml

@@ -22,4 +22,4 @@ mcp_servers:
   - name: "mcp-file"
     url: "http://mock-mcp:3001"
     authorization_headers:
-      Authorization: "/tmp/mcp-secret-token"
+      Authorization: "/tmp/mcp-token"

tests/e2e/configuration/server-mode/lightspeed-stack-mcp.yaml

@@ -30,7 +30,7 @@ mcp_servers:
   - name: "mcp-file"
     url: "http://mock-mcp:3001"
     authorization_headers:
-      Authorization: "/tmp/mcp-secret-token"
+      Authorization: "/tmp/mcp-token"
   - name: "mcp-client"
     url: "http://mock-mcp:3001"
     authorization_headers:

tests/e2e/features/mcp.feature

@@ -10,7 +10,7 @@ Feature: MCP tests
   @MCPFileAuthConfig
   Scenario: Check if tools endpoint succeeds when MCP file-based auth token is passed 
     Given The system is in default state
-    And The mcp-file mcp server Authorization header is set to "/tmp/mcp-secret-token"
+    And The mcp-file mcp server Authorization header is set to "/tmp/mcp-token"
     When I access REST API endpoint "tools" using HTTP GET method
     Then The status code of the response is 200
     And The body of the response contains mcp-file
@@ -19,7 +19,7 @@ Feature: MCP tests
   @MCPFileAuthConfig
   Scenario: Check if query endpoint succeeds when MCP file-based auth token is passed
     Given The system is in default state
-    And The mcp-file mcp server Authorization header is set to "/tmp/mcp-secret-token"
+    And The mcp-file mcp server Authorization header is set to "/tmp/mcp-token"
     And I capture the current token metrics
     When I use "query" to ask question
     """
@@ -35,7 +35,7 @@ Feature: MCP tests
   @MCPFileAuthConfig
   Scenario: Check if streaming_query endpoint succeeds when MCP file-based auth token is passed
     Given The system is in default state
-    And The mcp-file mcp server Authorization header is set to "/tmp/mcp-secret-token"
+    And The mcp-file mcp server Authorization header is set to "/tmp/mcp-token"
     And I capture the current token metrics
     When I use "streaming_query" to ask question
     """
@@ -51,7 +51,7 @@ Feature: MCP tests
   @InvalidMCPFileAuthConfig
   Scenario: Check if tools endpoint reports error when MCP file-based invalid auth token is passed 
     Given The system is in default state
-    And The mcp-file mcp server Authorization header is set to "/tmp/invalid-mcp-secret-token"
+    And The mcp-file mcp server Authorization header is set to "/tmp/invalid-mcp-token"
     When I access REST API endpoint "tools" using HTTP GET method
     Then The status code of the response is 401
     And The body of the response is the following
@@ -68,7 +68,7 @@ Feature: MCP tests
   @InvalidMCPFileAuthConfig
   Scenario: Check if query endpoint reports error when MCP file-based invalid auth token is passed 
     Given The system is in default state
-    And The mcp-file mcp server Authorization header is set to "/tmp/invalid-mcp-secret-token"
+    And The mcp-file mcp server Authorization header is set to "/tmp/invalid-mcp-token"
     When I use "query" to ask question
     """
     {"query": "Say hello", "model": "{MODEL}", "provider": "{PROVIDER}"}
@@ -88,7 +88,7 @@ Feature: MCP tests
   @InvalidMCPFileAuthConfig
   Scenario: Check if streaming_query endpoint reports error when MCP file-based invalid auth token is passed 
     Given The system is in default state
-    And The mcp-file mcp server Authorization header is set to "/tmp/invalid-mcp-secret-token"
+    And The mcp-file mcp server Authorization header is set to "/tmp/invalid-mcp-token"
     When I use "streaming_query" to ask question
     """
     {"query": "Say hello", "model": "{MODEL}", "provider": "{PROVIDER}"}