Support wildcard in Allowed Origins

Checklist

• I could not find a solution in the existing issues or docs.
• I agree to follow this project's Code of Conduct.

Description

We use preview deployments for work in progress on our development and staging environments. Each preview deployment gets its own unique URL, which currently means we need to manually add every new preview URL to the Allowed origins configuration.

It would be very useful to support wildcard in Allowed origins.

This would allow all preview deployments to work without requiring us to update the Hanko configuration for every deployment.

We understand that allowing wildcard origin wont allow us use the passkeys/WebAuthn, and we're fine with that limitation for preview environments. The other authentication methods would still be fully usable.

Use case

• Production uses a fixed, explicitly configured origin.
• Dev/staging use dynamically generated preview URLs.
• We would like to allow all preview URLs with a single wildcard entry.
• Passkeys are not required in these preview environments.

This would make preview deployments significantly easier to use and remove the need for manual configuration whenever a new preview deployment is created.

Note

Wildcard origin is already supported in self-hosted Hanko. It would be great to have the same capability available in Hanko Cloud as well.

Hanko Version

Hanko Cloud - v3.0.4