Hey team, we're trying to deploy a staging environ...
# ory-network
m
Hey team, we're trying to deploy a staging environment for testing purposes and we're using a separate Developer Ory project. Our frontend is a static site, and we have our own custom login pages. We're using
@ory/client
v1.1.38
to connect with Ory Network and APIs. We've also set the CORS as instructed here: https://www.ory.sh/docs/guides/cors#enable-cors But we're still blocked by CORS: •
/self-service/login/browser?refresh=false
this endpoint works and we're able to render our own login page • But when submitting the login form
/self-service/login?flow=<id>
this endpoint is blocked by CORS: No 'Access-Control-Allow-Origin' header is present on the requested resource Is there something I missed? Hope you can help us. Thanks!
cc @jolly-ocean-27001
d
Have you managed to fix it? we have the same problem
b
We also have custom UI and have multiple environments with each environment configured to a separate Ory Network project. • one for localhost (all urls in configuration pointing to localhost, using ory tunnel for development) • one for stage, scale plan so we can configure a custom domain, required to make CORS work • one for prod, also scale plan with custom domain We configured like this: stage-login.ourdomain.com --> CNAME to our stage project custom UI hosted at: account.stage-login.ourdomain.com login.ourdomain.com --> CNAME to our prod project custom UI at: account.login.ourdomain.com ( also we are using config-as-code to keep the configuration the same between each ory network project, minimizing clickety-click in the Ory GUI )
h
Wait, @hundreds-match-36539 are you saying that for each environment, including dev environment, we'll need to match the plan for production? Having to pay $600+/mo for two users to use the environment sounds like an anti-pattern