To deploy your project to staging or production, some changes need to be made in order to ensure stricter security.
.env
file is recommended, allowing for dynamic value assignment based on your environment. Below are the variables you’ll need to modify for Corbado:
pro-
. This is passed to the UI components during initialization.corbado1_
. It’s used to access Corbado’s Backend API.https://www.acme.com
for a live application.
localhost
.pro-123456789.frontendapi.cloud.corbado.io
) to another (the canonical name, e.g. auth.acme.com
).
<project ID>.frontendapi.cloud.corbado.io
ensuring SameSite cookies work properly, which enhances the security. Moreover, it improves UX as users see a familiar URL in the browser.
<project ID>.frontendapi.cloud.corbado.io
which might be confusing for users if they see this Relying Party ID in a Touch ID / Face ID / Android biometrics modal / popup. To update the Relying Party ID to your desired value, you would need a CNAME which is a subdomain of your Relying Party ID.
<project ID>.frontendapi.cloud.corbado.io
. Choose an approriate “TTL”, often default is fine.session-token
is a JWT) which will be set to the CNAME.
<project ID>.frontendapi.cloud.corbado.io
.