Fiware PEP Proxy Wilma

https://fiware-pep-proxy.readthedocs.io/en/latest/
Admin
Wilma is a PEP Proxy that enforces access control to backend applications by combining with security...
Tokens:5,667
Snippets:47
Trust Score:8.3
Update:1 year ago
Show doc for...
Tokens:
Raw
### HTTP Request Examples with Token Headers

Source: https://fiware-pep-proxy.readthedocs.io/en/latest/admin_guide

Examples of making HTTP requests to the PEP Proxy, demonstrating the use of both `Authorization: Bearer` and `X-Auth-Token` headers for authentication.

```http
GET / HTTP/1.1
Host: proxy_host
Authorization: Bearer z2zXk...ANOXvZrmvxvSg


```

```http
GET / HTTP/1.1
Host: proxy_host
X-Auth-Token:z2zXk...ANOXvZrmvxvSg


```

--------------------------------

### Start PEP Proxy Server

Source: https://fiware-pep-proxy.readthedocs.io/en/latest/index

Starts the PEP Proxy server using npm. Requires Node.js and npm to be installed, and dependencies to be installed.

```bash
sudo npm start
```

--------------------------------

### Start PEP Proxy with npm

Source: https://fiware-pep-proxy.readthedocs.io/en/latest/admin_guide

This command starts the PEP Proxy application using npm. Administrative permissions are required if running on TCP Port 80.

```bash
npm start
```

--------------------------------

### cURL Command Examples for PEP Proxy Testing

Source: https://fiware-pep-proxy.readthedocs.io/en/latest/admin_guide

Command-line examples using `curl` to test the PEP Proxy integration, showing how to include authentication tokens via `X-Auth-Token` or `Authorization` headers.

```bash
curl --header "X-Auth-Token: z2zXk...ANOXvZrmvxvSg" http://proxy_host

```

```bash
curl --header "Authorization: Bearer z2zXk...ANOXvZrmvxvSg" http://proxy_host

```

--------------------------------

### Run PEP Proxy Server using forever.js

Source: https://fiware-pep-proxy.readthedocs.io/en/latest/admin_guide

This command starts the PEP Proxy server using 'forever.js', ensuring it runs continuously in the background. This is typically used after installing forever.js.

```bash
forever start server.js
```

--------------------------------

### Basic PEP Proxy Configuration Example

Source: https://fiware-pep-proxy.readthedocs.io/en/latest/admin_guide

This JavaScript snippet shows a basic configuration for the PEP Proxy. It includes settings for Identity Management host, application host and port, PEP proxy credentials, and a flag for checking permissions. This configuration should be saved as 'config.js'.

```javascript
var config = {};

config.idm_host = 'https://account.lab.fiware.org';

config.app.host = 'www.google.es';
config.app.port = '80';

config.pep.app_id = 'my_app_id';
config.pep.username = 'pepProxy';
config.pep.password = 'pepProxy';

config.check_permissions = false;

module.exports = config;
```

--------------------------------

### Install PEP Proxy Dependencies with npm

Source: https://fiware-pep-proxy.readthedocs.io/en/latest/admin_guide

This command navigates into the PEP Proxy directory and installs all necessary Node.js dependencies using npm. Ensure Node.js and npm are installed.

```bash
cd fiware-pep-proxy
npm install
```

--------------------------------

### Install FIWARE PEP Proxy from Source (Bash)

Source: https://context7.com/context7/fiware-pep-proxy_readthedocs_io_en/llms.txt

Steps to clone the repository, install dependencies, configure the proxy, and start the service using npm. Requires Node.js and npm.

```bash
# Clone the repository
git clone https://github.com/ging/fiware-pep-proxy.git

# Install dependencies
cd fiware-pep-proxy/
npm install

# Configure the proxy
cp config.js.template config.js

# Start the proxy (requires sudo for port 80)
sudo npm start
```

--------------------------------

### Install forever.js for Production Deployment

Source: https://fiware-pep-proxy.readthedocs.io/en/latest/admin_guide

This command installs the 'forever.js' package globally, which is recommended for running the PEP Proxy in a production environment. This requires sudo privileges.

```bash
sudo npm install forever -g
```

--------------------------------

### Example HTTP Request with X-Auth-Token

Source: https://fiware-pep-proxy.readthedocs.io/en/latest/index

An example of an HTTP GET request to the proxy host using the `X-Auth-Token` header for authentication. This illustrates the expected format of a request.

```http
GET / HTTP/1.1
Host: proxy_host
X-Auth-Token:z2zXk...ANOXvZrmvxvSg
```

--------------------------------

### Nginx Configuration for PEP Proxy Integration

Source: https://fiware-pep-proxy.readthedocs.io/en/latest/admin_guide

An example Nginx server configuration demonstrating how to use the `auth_request` module to direct requests through the PEP Proxy for token validation before proxying to the backend application (e.g., Orion).

```nginx
server {
    listen 80;
    server_name example.org;

    location / {
        set $req_uri "$uri";
        auth_request /_check_oauth2_token;
        proxy_pass http://orion:1026;
    }

    location = /_check_oauth2_token {
        internal;
        proxy_method $request_method;
        proxy_pass_request_headers on;
        proxy_set_header Content-Length "";
        proxy_pass_request_body off;
        rewrite (.*) $req_uri break;
        proxy_pass http://wilma:1027;
    }
}

```

--------------------------------

### Clone PEP Proxy Repository using Git

Source: https://fiware-pep-proxy.readthedocs.io/en/latest/admin_guide

This command clones the PEP Proxy repository from GitHub. Ensure you have Git installed and configured.

```bash
git clone https://github.com/ging/fiware-pep-proxy
```

--------------------------------

### Production Deployment with forever.js in Bash

Source: https://context7.com/context7/fiware-pep-proxy_readthedocs_io_en/llms.txt

Demonstrates how to deploy and manage the PEP Proxy as a daemon process in a production environment using forever.js. This includes installation, starting, listing, stopping, and viewing logs.

```bash
# Install forever globally
sudo npm install forever -g

# Start PEP Proxy as a daemon
forever start server.js

# Check running processes
forever list

# Stop the process
forever stop server.js

# View logs
forever logs server.js
```

--------------------------------

### Example HTTP Request with Authorization Header

Source: https://fiware-pep-proxy.readthedocs.io/en/latest/index

An example of an HTTP GET request to the proxy host using the `Authorization: Bearer` header for authentication. This shows an alternative authentication method.

```http
GET / HTTP/1.1
Host: proxy_host
Authorization: Bearer z2zXk...ANOXvZrmvxvSg
```

--------------------------------

### List Running PEP Proxy Processes with forever

Source: https://fiware-pep-proxy.readthedocs.io/en/latest/admin_guide

A command to list currently running Node.js processes managed by `forever`, useful for system administrators to monitor the PEP Proxy's status.

```bash
 forever list

```

--------------------------------

### Send GET Request with X-Auth-Token Header

Source: https://fiware-pep-proxy.readthedocs.io/en/latest/index

Sends a GET request to the proxy host with an `X-Auth-Token` header. This is an example of how to authenticate requests to the proxy.

```bash
curl --header "X-Auth-Token: z2zXk...ANOXvZrmvxvSg" http://proxy_host
```

--------------------------------

### Verify Disk Space with df command

Source: https://fiware-pep-proxy.readthedocs.io/en/latest/admin_guide

A standard UNIX command to check available disk space on the system, ensuring sufficient resources for the PEP Proxy and other operations.

```bash
df

```

--------------------------------

### Install PEP Proxy Dependencies

Source: https://fiware-pep-proxy.readthedocs.io/en/latest/index

Installs project dependencies using npm after navigating into the cloned repository directory. Requires Node.js and npm to be installed.

```bash
cd fiware-pep-proxy/
npm install
```

--------------------------------

### Advanced PEP Proxy Authorization Configuration

Source: https://fiware-pep-proxy.readthedocs.io/en/latest/admin_guide

This JavaScript snippet demonstrates an advanced configuration for PEP Proxy authorization, specifying the authorization provider (pdp) and related settings. This configuration is compatible with the oauth2 tokens engine.

```javascript
config.authorization = {
    enabled: false,
    pdp: 'idm', // idm|iShare|xacml|authzforce|opa
    header: undefined,
    azf: {
        protocol: 'http',
        host: 'localhost',
        port: 8080,
        custom_policy: undefined // use undefined to default policy checks (HTTP verb + path).
    }
};
```

--------------------------------

### Configure Identity Manager (IDM) for PEP Proxy

Source: https://fiware-pep-proxy.readthedocs.io/en/latest/admin_guide

This JSON snippet defines the configuration for connecting to an Identity Manager (IDM). It includes the host, port, and SSL status for the IDM. Proper IDM configuration is crucial for authentication and authorization in the PEP Proxy.

```json
{
    "host": "localhost",
    "port": 3005,
    "ssl": false
}
```

--------------------------------

### Check PEP Proxy Process Status with forever.js

Source: https://fiware-pep-proxy.readthedocs.io/en/latest/admin_guide

This command displays the current status of processes managed by 'forever.js', including the PEP Proxy server if it's running.

```bash
forever status
```

--------------------------------

### Clone PEP Proxy Repository

Source: https://fiware-pep-proxy.readthedocs.io/en/latest/index

Clones the fiware-pep-proxy repository from GitHub. Requires Git to be installed.

```bash
git clone https://github.com/ging/fiware-pep-proxy.git
```

--------------------------------

### User Information Headers Added by PEP Proxy

Source: https://fiware-pep-proxy.readthedocs.io/en/latest/admin_guide

Illustrates the additional HTTP headers that the PEP Proxy appends to forwarded requests once a user is authenticated, providing user details from the Identity Management (IdM) system.

```http
 X-Nick-Name: nickname of the user in IdM
 X-Display-Name: display name of user in IdM
 X-Roles: roles of the user in IdM
 X-Organizations: organizations in IdM


```

--------------------------------

### HTTP Request Examples with OAuth2 Token for PEP Proxy

Source: https://fiware-pep-proxy.readthedocs.io/en/latest/user_guide

Demonstrates two ways to send an OAuth2 access token obtained from FIWARE IDM GE to the PEP Proxy for request validation. These methods use either the 'Authorization: Bearer' header or the 'X-Auth-Token' header.

```HTTP
GET / HTTP/1.1
Host: proxy_host
Authorization: Bearer z2zXk...ANOXvZrmvxvSg

```

```HTTP
GET / HTTP/1.1
Host: proxy_host
X-Auth-Token:z2zXk...ANOXvZrmvxvSg

```

--------------------------------

### Define Protected Application Configuration for PEP Proxy

Source: https://fiware-pep-proxy.readthedocs.io/en/latest/admin_guide

This JSON snippet specifies the configuration for the application being protected by the PEP Proxy. It includes the application's host, port, and whether it uses SSL. This allows the PEP Proxy to correctly route and manage access to the protected resource.

```json
{
    "host": "www.fiware.org",
    "port": "80",
    "ssl": false // Use true if the app server listens in https
}
```

--------------------------------

### Make Authenticated Requests via PEP Proxy (Bash)

Source: https://context7.com/context7/fiware-pep-proxy_readthedocs_io_en/llms.txt

Examples of making authenticated requests to the PEP Proxy using cURL with either X-Auth-Token or Authorization Bearer headers.

```bash
# Using X-Auth-Token header
curl --header "X-Auth-Token: z2zXk...ANOXvZrmvxvSg" \
     http://proxy_host

# Using Authorization Bearer header
curl --header "Authorization: Bearer z2zXk...ANOXvZrmvxvSg" \
     http://proxy_host

# Example HTTP request format
# GET / HTTP/1.1
# Host: proxy_host
# Authorization: Bearer z2zXk...ANOXvZrmvxvSg
```

--------------------------------

### Configure CORS Options for PEP Proxy

Source: https://fiware-pep-proxy.readthedocs.io/en/latest/admin_guide

This JSON snippet defines the Cross-Origin Resource Sharing (CORS) options for the PEP Proxy. It specifies allowed origins, methods, headers, and credentials settings. This is essential for controlling how external domains can interact with the protected resources.

```json
{
    "origin": "*",
    "methods": "GET,HEAD,PUT,PATCH,POST,DELETE",
    "preflightContinue": false,
    "optionsSuccessStatus": 204,
    "allowedHeaders": "content-type,X-Auth-Token,Tenant-ID,Authorization,Fiware-Service,Fiware-ServicePath,NGSILD-Tenant,NGSILD-Path",
    "credentials": true
}
```

--------------------------------

### Integrate PEP Proxy with Nginx (JavaScript and Nginx)

Source: https://context7.com/context7/fiware-pep-proxy_readthedocs_io_en/llms.txt

Configuration to enable Nginx mode in PEP Proxy and the corresponding Nginx server block setup using the `auth_request` module to delegate authentication checks.

```javascript
// config.js - Enable Nginx mode
config.auth_for_nginx = true;
```

```nginx
# Nginx configuration
server {
    listen 80;
    server_name example.org;

    location / {
        set $req_uri "$uri";
        auth_request /_check_oauth2_token;
        proxy_pass http://orion:1026;
    }

    location = /_check_oauth2_token {
        internal;
        proxy_method $request_method;
        proxy_pass_request_headers on;
        proxy_set_header Content-Length "";
        proxy_pass_request_body off;
        rewrite (.*) $req_uri break;
        proxy_pass http://wilma:1027;
    }
}
```

--------------------------------

### Enable Nginx Auth for PEP Proxy

Source: https://fiware-pep-proxy.readthedocs.io/en/latest/admin_guide

Enables the PEP Proxy to respond with HTTP status '204 No Content' to Nginx when a valid token is provided, simplifying integration. This setting is crucial for the `auth_request` module in Nginx.

```javascript
config.auth_for_nginx = true;

```

--------------------------------

### Configure HTTPS and Error Handling for PEP Proxy

Source: https://fiware-pep-proxy.readthedocs.io/en/latest/admin_guide

This JSON snippet configures HTTPS settings, including certificate and key files, the port for HTTPS, and custom templates for error messages. It also specifies the content type for these error messages. This is useful for securing communication and customizing error responses.

```json
{
    "enabled": false,
    "cert_file": "cert/cert.crt",
    "key_file": "cert/key.key",
    "port": 443,
    "error_template" : "{\"type\": \"{{type}}\", \"title\": \"{{title}}\", \"detail\": \"{{message}}\"}",
    "error_content_type" : "application/json"
}
```

--------------------------------

### Configure Authorization Policy for PEP Proxy

Source: https://fiware-pep-proxy.readthedocs.io/en/latest/admin_guide

This JSON snippet configures the authorization policy for the PEP Proxy. It allows selection between Identity Manager (IdM) for basic authorization and Authzforce for advanced checks. It also includes settings for the Authzforce endpoint and an option for custom policy scripts.

```json
{
    "enabled": false,
    "pdp": "idm", // idm|authzforce
    "azf": {
        "protocol": "http",
        "host": "localhost",
        "port": 8080,
        "custom_policy": undefined
    }
}
```

--------------------------------

### Configure Organization Settings for PEP Proxy

Source: https://fiware-pep-proxy.readthedocs.io/en/latest/admin_guide

This JSON snippet configures organization-related settings for the PEP Proxy, specifically focusing on how services are identified. The `enabled` flag controls whether organization-specific headers are used, and `header` specifies the name of the header used for service identification.

```json
{
    "enabled": false,
    "header": "fiware-service"
}
```

--------------------------------

### Configure PEP Proxy Registration in Identity Manager

Source: https://fiware-pep-proxy.readthedocs.io/en/latest/admin_guide

This JSON snippet outlines the parameters required for registering the PEP Proxy within an Identity Manager. It includes essential details like application ID, username, password, and a secret for token validation. This is vital for secure communication between the PEP Proxy and the Identity Manager.

```json
{
    "app_id": "",
    "username": "",
    "password": "",
    "token": {
        "secret": ""
    },
    "trusted_apps": []
}
```

--------------------------------

### Send GET Request with Authorization Header

Source: https://fiware-pep-proxy.readthedocs.io/en/latest/index

Sends a GET request to the proxy host with an `Authorization: Bearer` header. This is an alternative method for authenticating requests to the proxy.

```bash
curl --header "Authorization: Bearer z2zXk...ANOXvZrmvxvSg" http://proxy_host
```

--------------------------------

### Docker Deployment of PEP Proxy in Bash

Source: https://context7.com/context7/fiware-pep-proxy_readthedocs_io_en/llms.txt

Provides commands for deploying the FIWARE PEP Proxy using Docker. This includes pulling the official image, running with basic configurations, and checking logs.

```bash
# Pull the official image
docker pull fiware/pep-proxy

# Run with basic configuration
docker run -d --name pep-proxy \
  -p 1027:1027 \
  -e PEP_PROXY_APP_HOST=backend.example.com \
  -e PEP_PROXY_APP_PORT=80 \
  -e PEP_PROXY_IDM_HOST=account.lab.fiware.org \
  -e PEP_PROXY_APP_ID=my_app_id \
  -e PEP_PROXY_USERNAME=pepProxy \
  -e PEP_PROXY_PASSWORD=pepProxyPassword \
  fiware/pep-proxy

# Check logs
docker logs -f pep-proxy
```

--------------------------------

### Configure Basic Authorization (JavaScript)

Source: https://context7.com/context7/fiware-pep-proxy_readthedocs_io_en/llms.txt

Configuration settings for enabling basic authorization in PEP Proxy, specifying the Policy Decision Point (PDP) and optional authorization force settings for Keyrock integration.

```javascript
// config.js
config.authorization = {
    enabled: true,
    pdp: 'idm', // Options: idm|iShare|xacml|authzforce|opa
    header: undefined, // Optional: tenant header for multi-tenant systems
    azf: {
        protocol: 'http',
        host: 'localhost',
        port: 8080,
        custom_policy: undefined // Use undefined for default policy checks
    }
};

// Multi-tenant authorization with tenant filtering
config.authorization = {
    enabled: true,
    pdp: 'idm',
    header: 'NGSILD-Tenant', // or 'fiware-service'
    azf: {
        protocol: 'http',
        host: 'localhost',
        port: 8080,
        custom_policy: undefined
    }
};
```

--------------------------------

### Configure PEP Proxy with Environment Variables in Bash

Source: https://context7.com/context7/fiware-pep-proxy_readthedocs_io_en/llms.txt

Sets up PEP Proxy configuration using environment variables for Docker deployments. This allows for dynamic configuration of backend host/port, Identity Management details, application credentials, and public paths.

```bash
# Docker environment configuration
docker run -e PEP_PROXY_APP_HOST=backend.example.com \
           -e PEP_PROXY_APP_PORT=80 \
           -e PEP_PROXY_IDM_HOST=account.lab.fiware.org \
           -e PEP_PROXY_IDM_PORT=443 \
           -e PEP_PROXY_IDM_SSL_ENABLED=true \
           -e PEP_PROXY_APP_ID=my_app_id \
           -e PEP_PROXY_USERNAME=pepProxy \
           -e PEP_PROXY_PASSWORD=pepProxyPassword \
           -e PEP_PROXY_AUTH_ENABLED=true \
           -e PEP_PROXY_PDP=idm \
           -e PEP_PROXY_PUBLIC_PATHS="/public/*,/health" \
           fiware/pep-proxy
```

--------------------------------

### Configure HTTPS Support (JavaScript)

Source: https://context7.com/context7/fiware-pep-proxy_readthedocs_io_en/llms.txt

Settings for enabling HTTPS support in PEP Proxy, specifying certificate and key file paths, port, and error response format.

```javascript
// config.js
config.pep_port = 80; // HTTP port when HTTPS disabled

config.https = {
    enabled: true,
    cert_file: "cert/cert.crt",
    key_file: "cert/key.key",
    port: 443,
    error_template: "{\"type\": \"{{type}}\", \"title\": \"{{title}}\", \"detail\": \"{{message}}\"}",
    error_content_type: "application/json"
};
```

--------------------------------

### Configure PEP Proxy for Authentication Only (JavaScript)

Source: https://context7.com/context7/fiware-pep-proxy_readthedocs_io_en/llms.txt

Basic configuration file for PEP Proxy, setting Identity Manager endpoint, protected application details, proxy credentials, and disabling authorization checks for Level 1 security.

```javascript
// config.js
var config = {};

// Identity Manager endpoint
config.idm_host = 'https://account.lab.fiware.org';

// Protected backend application
config.app.host = 'www.google.es';
config.app.port = '80';

// PEP Proxy credentials registered in IdM
config.pep.app_id = 'my_app_id';
config.pep.username = 'pepProxy';
config.pep.password = 'pepProxy';

// Disable authorization checks (authentication only)
config.check_permissions = false;

module.exports = config;
```

--------------------------------

### PEP Proxy API Usage

Source: https://fiware-pep-proxy.readthedocs.io/en/latest/index

This section details how to make requests to the PEP Proxy and the headers used for authentication. It also describes the additional headers that are added to forwarded requests once a user is authenticated.

```APIDOC
## PEP Proxy API Usage

### Description
Requests to the PEP Proxy require an `X-Auth-Token` header containing the OAuth access token obtained from FIWARE IDM GE. The proxy forwards authenticated requests and appends user information headers.

### Method
GET

### Endpoint
`/` (Root endpoint, can be any resource path)

### Parameters

#### Request Headers
- **X-Auth-Token** (string) - Required - The OAuth access token obtained from FIWARE IDM GE.
- **Authorization** (string) - Required - Alternative header for authentication, typically `Bearer <token>`.

### Request Example
```http
GET / HTTP/1.1
Host: proxy_host
X-Auth-Token: z2zXk...ANOXvZrmvxvSg
```

```http
GET / HTTP/1.1
Host: proxy_host
Authorization: Bearer z2zXk...ANOXvZrmvxvSg
```

#### cURL Example
```bash
curl --header "X-Auth-Token: z2zXk...ANOXvZrmvxvSg" http://proxy_host
```

### Response
#### Success Response (200)
Upon successful authentication, the forwarded request will include additional HTTP headers with user information:

- **X-Nick-Name** (string) - Nickname of the user in IdM.
- **X-Display-Name** (string) - Display name of the user in IdM.
- **X-Roles** (string) - Roles of the user in IdM.
- **X-Organizations** (string) - Organizations the user belongs to in IdM.

#### Response Example (Headers in Forwarded Request)
```http
X-Nick-Name: example_user
X-Display-Name: Example User
X-Roles: role1,role2
X-Organizations: org1,org2
```
```

--------------------------------

### Configure Public Paths (JavaScript)

Source: https://context7.com/context7/fiware-pep-proxy_readthedocs_io_en/llms.txt

Configuration array for defining paths that should bypass PEP Proxy's authentication and authorization checks.

```javascript
// config.js
config.public_paths = [
    '/public/*',
    '/static/css/',
    '/api/v1/health'
];
```

--------------------------------

### User Metadata Headers in HTTP

Source: https://context7.com/context7/fiware-pep-proxy_readthedocs_io_en/llms.txt

Illustrates HTTP headers added by the PEP Proxy after successful authentication, such as nickname, display name, roles, and organizations. These headers are then forwarded to the backend application.

```http
# After successful authentication, PEP Proxy adds these headers:
X-Nick-Name: john_doe
X-Display-Name: John Doe
X-Roles: admin,developer
X-Organizations: org1,org2

# Backend application receives enriched request
GET /api/resource HTTP/1.1
Host: backend.example.com
X-Nick-Name: john_doe
X-Display-Name: John Doe
X-Roles: admin,developer
X-Organizations: org1,org2
```

--------------------------------

### Advanced Authorization with Authzforce in JavaScript

Source: https://context7.com/context7/fiware-pep-proxy_readthedocs_io_en/llms.txt

Enables and configures advanced authorization using Authzforce with XACML policies. This involves specifying the protocol, host, port of the Authzforce server, and optionally a custom policy script.

```javascript
// config.js
config.authorization = {
    enabled: true,
    pdp: 'authzforce',
    azf: {
        protocol: 'http',
        host: 'authzforce.example.com',
        port: 8080,
        custom_policy: './policies/custom_policy.js' // Custom policy script
    }
};
```

--------------------------------

### Configure PEP Proxy Application Host and Port

Source: https://fiware-pep-proxy.readthedocs.io/en/latest/index

Configures the application host and port for the PEP Proxy by duplicating and modifying the `config.js` file. This specifies where authenticated requests will be forwarded.

```javascript
config.app_host = 'www.google.es'; // Hostname to forward authenticated requests
config.app_port = '80'; // Port where the HTTP server is running
```

--------------------------------

### Enable Organization Support in JavaScript

Source: https://context7.com/context7/fiware-pep-proxy_readthedocs_io_en/llms.txt

Enables multi-organization support within the PEP Proxy configuration. This involves setting an 'enabled' flag to true and specifying the header used for organization identification.

```javascript
// config.js
config.organizations = {
    enabled: true,
    header: "fiware-service"
};
```

--------------------------------

### Configure CORS Policies in JavaScript

Source: https://context7.com/context7/fiware-pep-proxy_readthedocs_io_en/llms.txt

Configures Cross-Origin Resource Sharing (CORS) policies for the PEP Proxy. This includes setting allowed origins, methods, headers, and other relevant options. It can be configured for broad access ('*') or restricted to specific domains.

```javascript
// config.js
config.corsOptions = {
    origin: "*", // Or specific origin: "http://example.com"
    methods: "GET,HEAD,PUT,PATCH,POST,DELETE",
    preflightContinue: false,
    optionsSuccessStatus: 204,
    allowedHeaders: "content-type,X-Auth-Token,Tenant-ID,Authorization,Fiware-Service,Fiware-ServicePath,NGSILD-Tenant,NGSILD-Path",
    credentials: true
};

// Restrict to specific domains
config.corsOptions = {
    origin: ["http://example1.com", /\.example2\.com$/],
    methods: "GET,POST,PUT,DELETE",
    allowedHeaders: "content-type,X-Auth-Token,Authorization",
    credentials: true,
    maxAge: 86400
};
```

--------------------------------

### Configure JWT Token Validation in JavaScript

Source: https://context7.com/context7/fiware-pep-proxy_readthedocs_io_en/llms.txt

Configures the PEP Proxy to validate JSON Web Tokens (JWT). This involves setting the application ID, username, password, and JWT secret key for token verification.

```javascript
// config.js
config.pep = {
    app_id: "application_id",
    username: "pepProxy",
    password: "pepProxyPassword",
    token: {
        secret: "your_jwt_secret_key"
    },
    trusted_apps: ["trusted_app_id_1", "trusted_app_id_2"]
};
```
Tokens:
Raw