Skip to content

Update wildcards-for-subdomains.mdx #371

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
nick-gagliardi wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Update wildcards-for-subdomains.mdx #371

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
196ead0
Update wildcards-for-subdomains.mdx
nick-gagliardi Dec 3, 2025
93c8a2a
Update wildcards-for-subdomains.mdx
BcnCarlos Dec 4, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 26 additions & 2 deletions main/docs/get-started/applications/wildcards-for-subdomains.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ You can use various placeholders to act as dynamic text entries in your URLs.

## How URL evaluation works

A URL containing an `{organization_name}` placeholder will only be evaluated when all the following the conditions are met:
A URL containing an `{organization_name}` placeholder will only be evaluated when all the following conditions are met:

* The application has the `organization_usage` set to `allow` or `require`
* A transaction was performed in the context of an organization (for example, initiating an authorization transaction with the organization parameter: `/authorize?organization=org_bVss9Do3994SIbiH&…`)
Expand Down Expand Up @@ -63,8 +63,32 @@ The following restrictions apply when using the `{organization_name}` placeholde
* A placeholder must not be prefixed nor suffixed with additional valid hostname characters. `https://prefix-{organization_name}-suffix.exampleco.com` will not work.
* A placeholder **must not** be used in conjunction with a wildcard in the URL. `https://{organization_name}.*.exampleco.com` will not work.

## Custom domain URL placeholders
Copy link

@dlozlla dlozlla Dec 5, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are few things missing:


You can use `{custom_domain.metadata.KEY}` as a placeholder to dynamically specify a URL based on metada associated with the Custom Domain used in the request. This allows you to support multiple custom domains with different application URLs within the same tenant.

For more information on configuring metadata, see [Use metadata to stay organized](/docs/customize/custom-domains/multiple-custom-domains/mcd-best-practices#use-metadata-to-stay-organized).

### Validation rules

The following restrictions apply when using Custom Domain placeholders:

* **Public prefix required**: The metadata key used in the placeholder must start with `public_` or `PUBLIC_` (for example, `{custom_domain.metadata.public_callback_subdomain}`). Keys without this prefix are ignored at runtime for security reasons.
* **Protocol**: The protocol of the URL must be `http` or `https`.
* **Location**: The placeholder must be located in the domain or subdomain component. It cannot be used in the URL path.
* Valid: `https://{custom_domain.metadata.public_app_url}.example.com/login`
* Invalid: `https://example.com/{custom_domain.metadata.public_path}`
* **Nesting**: You cannot access nested metadata properties. Only top-level keys are supported.
* **No wildcards**: A custom domain placeholder must not be used in conjunction with a wildcard (`*`) in the same URL.
* **Data type**: The value in the custom domain metadata must be a String. IF the key does not exist, or the value is not a String, the URL is ignored during validation.
Copy link

@dlozlla dlozlla Dec 5, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change IF -> If


### Using with Organization placeholders

You can combine the Custom Domain placeholder with the `{organization_name}` placeholder, as long as your flow supports it. Both placeholders are evaluated and replaced at runtime.


## Learn more

* [Confidential and Public Applications](/docs/get-started/applications/confidential-and-public-applications)
* [First-Party and Third-Party Applications](/docs/get-started/applications/confidential-and-public-applications/first-party-and-third-party-applications)
* [Enable Third-Party Applications](/docs/get-started/applications/confidential-and-public-applications/enable-third-party-applications)
* [Enable Third-Party Applications](/docs/get-started/applications/confidential-and-public-applications/enable-third-party-applications)
Loading