General Information
Policy Type
Endpoints
List Policies
Add Policy
Update Policy
Delete Policy
List Policies
Endpoint
Request
Headers
| Header | Value |
|---|---|
| Authorization | Bearer {token} |
Path Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| projectName | string | Yes | Project name |
| apiProxyName | string | Yes | API Proxy name |
Response
Success Response (200 OK)
cURL Example
Add Policy
Endpoint
Request
Headers
| Header | Value |
|---|---|
| Authorization | Bearer {token} |
| Content-Type | application/json |
Path Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| projectName | string | Yes | Project name |
| apiProxyName | string | Yes | API Proxy name |
| policyName | string | Yes | Policy name |
Request Body
Full JSON Body Example - Full Validation
Full JSON Body Example - Clear SAML After Validation
Request Body Fields
operationMetadata
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
| targetScope | string | Yes | - | Policy scope: ALL or ENDPOINT |
| targetEndpoint | string | No* | - | Endpoint path (required if targetScope=ENDPOINT) |
| targetEndpointHTTPMethod | string | No* | - | HTTP method (required if targetScope=ENDPOINT) |
| targetPipeline | string | Yes | - | Pipeline: REQUEST, RESPONSE, or ERROR |
| deploy | boolean | No | true | Whether to deploy after adding policy |
| deployTargetEnvironmentNameList | array | No | [] | List of environment names to deploy to |
| order | integer | No | null | Policy execution order (starts from 1) |
ALL- Policy applies to all endpointsENDPOINT- Policy applies only to specified endpoint
REQUEST- Executes in request pipeline (validates request SAML)RESPONSE- Executes in response pipeline (validates response SAML)ERROR- Executes in error pipeline
GET,POST,PUT,DELETE,PATCH,OPTIONS,HEAD
policy
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
| type | string | Yes | - | Policy type: policy-saml-validation |
| description | string | No | - | Policy description |
| active | boolean | No | true | Whether policy is active |
| keyStoreName | string | Yes | - | Keystore name for SAML signature validation |
| allowUnknownSigner | boolean | No | false | Allow unknown signer for SAML validation |
| clearSaml | boolean | No | false | Clear SAML assertion after validation |
| clearSamlPath | string | No* | null | XPath to SAML assertion to clear (required if clearSaml=true) |
Note
keyStoreNameis required and must reference a valid KeyStore containing SAML signing certificates.- KeyStore name is automatically resolved to KeyStore ID (searches in project KeyStores first, then global KeyStores).
- If
clearSaml: true,clearSamlPathis required (XPath expression to locate SAML assertion).
XPath Examples
/soap:Envelope/soap:Header/wsse:Security/saml:Assertion- SOAP header SAML assertion//saml:Assertion- Anywhere in document/root/saml:Assertion- Root element SAML assertion
Response
Success Response (200 OK)
cURL Example
Update Policy
Endpoint
Request
Headers
| Header | Value |
|---|---|
| Authorization | Bearer {token} |
| Content-Type | application/json |
Path Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| projectName | string | Yes | Project name |
| apiProxyName | string | Yes | API Proxy name |
| policyName | string | Yes | Policy name |
Request Body
Full JSON Body Example
Response
Success Response (200 OK)
Delete Policy
Endpoint
Request
Headers
| Header | Value |
|---|---|
| Authorization | Bearer {token} |
| Content-Type | application/json |
Path Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| projectName | string | Yes | Project name |
| apiProxyName | string | Yes | API Proxy name |
| policyName | string | Yes | Policy name |
Request Body
Full JSON Body Example
Response
Success Response (200 OK)
Notes and Warnings
-
KeyStore:
keyStoreNamemust reference a valid KeyStore containing SAML signing certificates- KeyStore name is automatically resolved to KeyStore ID (searches in project KeyStores first, then global KeyStores)
- KeyStore must contain public keys or certificates for signature validation
- Certificates must match the signer’s certificate used in SAML assertion
-
Signature Validation:
- Validates SAML assertion signature using certificates from KeyStore
- Signature must be valid and certificate must be trusted
- Assertion must not be expired
-
Unknown Signer:
- When
allowUnknownSigner: false, only signers with certificates in KeyStore are allowed - When
allowUnknownSigner: true, validation proceeds even if signer is not in KeyStore (less secure)
- When
-
Clear SAML:
- When
clearSaml: true, SAML assertion is removed after validation clearSamlPathmust be a valid XPath expression pointing to SAML assertion- Useful for removing sensitive SAML data before forwarding request
- When
-
XPath:
clearSamlPathmust be a valid XPath expression- Supports namespaces (e.g.,
soap:Envelope,saml:Assertion) - Use absolute paths for precise location
-
SAML Format:
- Supports SAML 1.1 and SAML 2.0 assertions
- Supports SAML assertions in SOAP headers (WS-Security)
- Supports SAML assertions in HTTP headers or body
- Performance: SAML validation adds processing overhead. Use for necessary validation only.
-
Pipeline:
REQUESTpipeline validates SAML in request before processingRESPONSEpipeline validates SAML in response before sending to client- Validation failure results in 401 Unauthorized or 403 Forbidden response
- Error Handling: Invalid SAML assertion or signature causes validation to fail
-
Deployment: Policy changes require deployment to take effect. Set
deploy: trueor deploy manually.
Related Documentation
- List Policies - List all policies
- Add Policy - General policy addition guide
- Update Policy - General policy update guide
- Delete Policy - General policy deletion guide
- OIDC Authentication Policy - OIDC Authentication
- JWT Authentication Policy - JWT Token Authentication

