v3.9.1 v3.9 v3.8.4 v3.8.3 v3.8.2 v3.8.1 v3.8 v3.7.2 v3.7.1 v3.7 v3.6
Auto Light Dark
Auto Light Dark
v3.9.1 v3.9 v3.8.4 v3.8.3 v3.8.2 v3.8.1 v3.8 v3.7.2 v3.7.1 v3.7 v3.6
Breadcrumbs

Web Origins (CORS Support) for each OIDC application

To improve the security posture of your OIDC integrations, version 3.8.4 introduces a dedicated configuration field for Web Origins. This field allows the VeridiumID server to validate the Origin header sent by browsers during cross-origin requests.
Setting is available in Admin / Application / Add OIDC application flow.

Key Configuration Rules:

  • Restricted Access: When one or more URLs are specified, the system will only grant access if the request origin matches an entry in the list.

  • Permissive Access: Leaving the field empty defaults to a wildcard (*), allowing all origins. This is intended for testing or internal services only.

  • Validation Logic: If a request is made from an unauthorized origin (e.g., www.untrusted-site.com), the CORS validation will fail, and the request will be rejected by the VeridiumID server.

Configuration Example:

  1. Requirement: Allow access only for a specific Veridium Manager instance.

  2. Configuration: Enter https://[env].veridium-dev.com:[port] into the Web Origins field.

  3. Result: Access is granted for requests originating from that specific domain. All other requests, such as those from www.google.com, are automatically denied.

    image-20260210-100525.png


Last updated: