Improviing integration so that we can move prebid and nextjs as integrations

Author: aram356

Cargo.lock

@@ -16,12 +16,12 @@ default-members = [
 debug = 1
 
 [workspace.dependencies]
+async-trait = "0.1"
 base64 = "0.22"
 brotli = "8.0"
 bytes = "1.10"
 chacha20poly1305 = "0.10"
 chrono = "0.4.42"
-async-trait = "0.1"
 config = "0.15.18"
 cookie = "0.18.1"
 derive_more = { version = "2.0", features = ["display", "error"] }
@@ -35,13 +35,14 @@ handlebars = "6.3.2"
 hex = "0.4.3"
 hmac = "0.12.1"
 http = "1.3.1"
+jose-jwk = "0.1.2"
 log = "0.4.28"
 log-fastly = "0.11.9"
 lol_html = "2.7.0"
+once_cell = "1.19"
 pin-project-lite = "0.2"
-regex = "1.12.2"
-jose-jwk = "0.1.2"
 rand = "0.8"
+regex = "1.12.2"
 serde = { version = "1.0", features = ["derive"] }
 serde_json = "1.0.145"
 sha2 = "0.10.9"

Cargo.toml

@@ -1,29 +1,30 @@
-# Trusted Server 
+# Trusted Server
 
-:information_source: Trusted Server is an open-source, cloud based orchestration framework and runtime for publishers. It moves code execution and operations that traditionally occurs in browsers (via 3rd party JS) to secure, zero-cold-start [WASM](https://webassembly.org) binaries running in [WASI](https://github.com/WebAssembly/WASI) supported environments. It importantly gives publishers benefits such as: dramatically increasing control over how and who they share their data with (while maintaining user-privacy compliance), increasing revenue from inventory inside cookie restricted or non-JS environments, ability to serve all assets under 1st party context, and provides secure cryptographic functions to ensure trust across the programmatic ad ecosystem. 
+:information_source: Trusted Server is an open-source, cloud based orchestration framework and runtime for publishers. It moves code execution and operations that traditionally occurs in browsers (via 3rd party JS) to secure, zero-cold-start [WASM](https://webassembly.org) binaries running in [WASI](https://github.com/WebAssembly/WASI) supported environments. It importantly gives publishers benefits such as: dramatically increasing control over how and who they share their data with (while maintaining user-privacy compliance), increasing revenue from inventory inside cookie restricted or non-JS environments, ability to serve all assets under 1st party context, and provides secure cryptographic functions to ensure trust across the programmatic ad ecosystem.
 
 Trusted Server is the new execution layer for the open-web, returning control of 1st party data, security, and overall user-experience back to publishers.
 
 At this time, Trusted Server is designed to work with Fastly Compute. Follow these steps to configure Fastly Compute and deploy it.
 
 ## Getting Started: Edge-Cloud Support on Fastly
+
 - Create account at Fastly if you don’t have one - manage.fastly.com
-- Log in to the Fastly control panel. 
-    - Go to Account > API tokens > Personal tokens. 
-    - Click Create token
-    - Name the Token
-    - Choose User Token
-    - Choose Global API Access
-    - Choose what makes sense for your Org in terms of Service Access
-    - Copy key to a secure location because you will not be able to see it again
-
-- Create new Compute Service 
-    - Click Compute and Create Service 
-    - Click “Create Empty Service” (below main options) 
-    - Add your domain of the website you’ll be testing or using and click update
-    - Click on “Origins” section and add your ad-server / SSP integration information as hostnames (note after you save this information you can select port numbers and TLS on/off) 
-    - IMPORTANT: when you enter the FQDN or IP ADDR information and click Add you need to enter a “Name” in the first field that will be referenced in your code so something like “my_ad_integration_1” 
-    - 
+- Log in to the Fastly control panel.
+  - Go to Account > API tokens > Personal tokens.
+  - Click Create token
+  - Name the Token
+  - Choose User Token
+  - Choose Global API Access
+  - Choose what makes sense for your Org in terms of Service Access
+  - Copy key to a secure location because you will not be able to see it again
+
+- Create new Compute Service
+  - Click Compute and Create Service
+  - Click “Create Empty Service” (below main options)
+  - Add your domain of the website you’ll be testing or using and click update
+  - Click on “Origins” section and add your ad-server / SSP integration information as hostnames (note after you save this information you can select port numbers and TLS on/off)
+  - IMPORTANT: when you enter the FQDN or IP ADDR information and click Add you need to enter a “Name” in the first field that will be referenced in your code so something like “my_ad_integration_1”
+  -
 
 :warning: With a dev account, Fastly gives you a test domain by default, but you’re also able to create a CNAME to your own domain when you’re ready, along with 2 free TLS certs (non-wildcard). Note that Fastly Compute ONLY accepts client traffic via TLS, though origins and backends can be non-TLS.
 
@@ -38,28 +39,33 @@ At this time, Trusted Server is designed to work with Fastly Compute. Follow the
 ```sh
 /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
 ```
+
 ### Fastly CLI
 
-#### Install Fastly CLI 
+#### Install Fastly CLI
+
 ```sh
 brew install fastly/tap/fastly
 ```
 
-#### Verify Installation and Version 
+#### Verify Installation and Version
+
 ```sh
 fastly version
 ```
 
 :warning: fastly cli version should be at least v12.1.0
 
 #### Create profile and follow interactive prompt for pasting your API Token created earlier:
-```sh	
+
+```sh
 fastly profile create
 ```
 
 ### Rust
 
 #### Install Rust with asdf (our preference)
+
 ```sh
 brew install asdf
 asdf plugin add rust
@@ -70,6 +76,7 @@ asdf reshim
 ### NodeJS
 
 #### Install NodeJS with asdf
+
 ```sh
 brew install asdf
 asdf plugin add nodejs
@@ -79,34 +86,39 @@ asdf reshim
 
 #### Fix path for Bash
 
-Edit ~/.bash_profile to add path for asdf shims: 
+Edit ~/.bash_profile to add path for asdf shims:
+
 ```sh
 export PATH="${ASDF_DATA_DIR:-$HOME/.asdf}/shims:$PATH"
 ```
 
 #### Fix path for ZSH
 
-Edit ~/.zshrc to add path for asdf shims: 
+Edit ~/.zshrc to add path for asdf shims:
+
 ```sh
 export PATH="${ASDF_DATA_DIR:-$HOME/.asdf}/shims:$PATH"
 ```
 
 #### Other shells
-See https://asdf-vm.com/guide/getting-started.html#_2-configure-asdf
 
+See https://asdf-vm.com/guide/getting-started.html#_2-configure-asdf
 
-### Clone Trusted Server and Configure Build 
+### Clone Trusted Server and Configure Build
 
 #### Clone Project (assumes you have 'git' installed on your system)
+
 ```sh
 git clone [email protected]:IABTechLab/trusted-server.git
 ```
 
 ### Configure
+
 #### Edit configuration files
+
 :information_source: Note that you'll have to edit the following files for your setup:
 
-- fastly.toml (service ID, author, description, Config/Secret Store IDs for request signing) 
+- fastly.toml (service ID, author, description, Config/Secret Store IDs for request signing)
 - trusted-server.toml (KV store ID names - optional, request signing configuration)
 
 ### Build
@@ -124,11 +136,13 @@ fastly compute publish
 ## Devleopment
 
 #### Install viceroy for running tests
+
 ```sh
 cargo install viceroy
 ```
 
 #### Run Fastly server locally
+
 - Review configuration for [local_server](fastly.toml#L16)
 - Review env variables overrides in [.env.dev](.env.dev)
 
@@ -141,13 +155,15 @@ fastly -i compute serve
 ```
 
 #### Tests
+
 ```sh
 cargo test
 ```
 
 :warning: if test fails `viceroy` will not display line number of the failed test. Rerun it with `cargo test_details`.
 
 #### Additional Rust Commands
+
 - `cargo fmt`: Ensure uniform code formatting
 - `cargo clippy`: Ensure idiomatic code
 - `cargo check`: Ensure compilation succeeds on Linux, MacOS, Windows and WebAssembly
@@ -166,6 +182,7 @@ Request signing requires Fastly Config Store and Secret Store for key management
    - Secret Store: `signing_keys` - stores private signing keys
 
 2. **Configure in trusted-server.toml**:
+
 ```toml
 [request_signing]
 enabled = true  # Set to true to enable request signing
@@ -187,7 +204,6 @@ Once configured, the following endpoints are available:
 - **`POST /admin/keys/rotate`**: Generates and activates a new signing key
   - Optional body: `{"kid": "custom-key-id"}` (auto-generates date-based ID if omitted)
   - Response includes new key ID, previous key ID, and active keys list
-  
 - **`POST /admin/keys/deactivate`**: Deactivates or deletes a key
   - Request body: `{"kid": "key-to-deactivate", "delete": false}`
   - Set `delete: true` to permanently remove the key (also deactivates it)
@@ -196,9 +212,9 @@ Once configured, the following endpoints are available:
 
 ## First-Party Endpoints
 
- - `/first-party/ad` (GET): returns HTML for a single slot (`slot`, `w`, `h` query params). The server inspects returned creative HTML and rewrites:
-  - All absolute images and iframes to `/first-party/proxy?tsurl=<base-url>&<original-query-params>&tstoken=<sig>` (1×1 pixels are detected server‑side heuristically for logging). The `tstoken` is derived from encrypting the full target URL and hashing it.
- - `/third-party/ad` (POST): accepts tsjs ad units and proxies to Prebid Server.
+- `/first-party/ad` (GET): returns HTML for a single slot (`slot`, `w`, `h` query params). The server inspects returned creative HTML and rewrites:
+- All absolute images and iframes to `/first-party/proxy?tsurl=<base-url>&<original-query-params>&tstoken=<sig>` (1×1 pixels are detected server‑side heuristically for logging). The `tstoken` is derived from encrypting the full target URL and hashing it.
+- `/third-party/ad` (POST): accepts tsjs ad units and proxies to Prebid Server.
 - `/first-party/proxy` (GET): unified proxy for resources referenced by creatives.
   - Query params:
     - `tsurl`: Target URL without query (base URL) — required
@@ -223,11 +239,12 @@ Once configured, the following endpoints are available:
 
 - Publisher origin proxy (`handle_publisher_request`): retrieves/generates the synthetic ID, stamps the response with `X-Synthetic-*` headers, and sets the `synthetic_id` cookie (Secure, SameSite=Lax) when absent so subsequent creative and click proxies can propagate the identifier.
 
- Notes
- - Rewriting uses `lol_html`. Only absolute and protocol‑relative URLs are rewritten; relative URLs are left unchanged.
- - For the proxy endpoint, the base URL is carried in `tsurl`, the original query parameters are preserved individually, and `tstoken` authenticates the reconstructed full URL.
- - Synthetic identifiers are generated by `crates/common/src/synthetic.rs` and are surfaced in three places: publisher responses (headers + cookie), creative proxy target URLs (`synthetic_id` query param), and click redirect URLs. This ensures downstream integrations can correlate impressions and clicks without direct third-party cookies.
+Notes
+
+- Rewriting uses `lol_html`. Only absolute and protocol‑relative URLs are rewritten; relative URLs are left unchanged.
+- For the proxy endpoint, the base URL is carried in `tsurl`, the original query parameters are preserved individually, and `tstoken` authenticates the reconstructed full URL.
+- Synthetic identifiers are generated by `crates/common/src/synthetic.rs` and are surfaced in three places: publisher responses (headers + cookie), creative proxy target URLs (`synthetic_id` query param), and click redirect URLs. This ensures downstream integrations can correlate impressions and clicks without direct third-party cookies.
 
 ## Integration Modules
 
-- See [`docs/integration_guide.md`](docs/integration_guide.md) for the full integration module guide, covering configuration, proxy routing, HTML shim hooks, and the `starlight` example implementation.
+- See [`docs/integration_guide.md`](docs/integration_guide.md) for the full integration module guide, covering configuration, proxy routing, HTML shim hooks, and the `testlight` example implementation.

README.md

@@ -43,6 +43,7 @@ urlencoding = { workspace = true }
 uuid = { workspace = true }
 validator = { workspace = true }
 ed25519-dalek = { workspace = true }
+once_cell = { workspace = true }
 
 [build-dependencies]
 config = { workspace = true }