This error is related to Content Security Policy (CSP) violations in the Ory Network. The CSP is a security measure implemented to prevent certain types of attacks, such as Cross-Site Scripting (XSS). Based on the information provided in the knowledge sources, there are a couple of potential reasons for this error: 1. Outdated CSP configuration: The error message you're seeing contains a CSP directive that doesn't match exactly with the most recent CSP configuration shown in the knowledge sources. This suggests that there might have been updates to the CSP settings that haven't been applied to your environment yet. 2. Cross-origin request issues: Ory Network implements strict CORS (Cross-Origin Resource Sharing) policies to enhance security. If your application is trying to submit a form to a domain that's not explicitly allowed in the CSP, you'll encounter this error. To resolve this issue, you can try the following: 1. Ensure that you're using the latest version of the Ory Network and that all configurations are up to date. 2. If you're developing locally, use the [Ory Tunnel](https://www.ory.sh/docs/getting-started/local-development) for development to avoid CORS issues. 3. If you're using a custom domain, make sure it's properly configured in your Ory Network project settings and that CORS is set up correctly for your domain. 4. Review your application's form submission targets and ensure they align with the allowed domains in the CSP directive. If the issue persists after trying these steps, you may need to contact Ory support for further assistance, as there might be specific configurations or recent changes affecting your project. For more information on CORS and CSP in Ory Network, you can refer to the [CORS documentation](https://www.ory.sh/docs/guides/cors) and [Custom Domains documentation](https://www.ory.sh/docs/guides/custom-domains#cors).

Thank you for providing that additional information. The fact that the issue only occurs in the Edge browser while other browsers work correctly suggests that this might be related to specific browser behavior or settings in Edge. However, I don't have enough information in the provided knowledge sources to give a definitive answer about Edge-specific issues with Ory. That being said, based on the information we do have, I can offer a few general suggestions: 1. Browser cookies and security settings: Edge might have stricter default settings for cookies or security that could interfere with the authentication process. You could try checking your Edge settings, particularly those related to cookies and site permissions. 2. Content Security Policy (CSP) interpretation: Different browsers may interpret or enforce CSP directives slightly differently. Edge might be more strict in its enforcement of the CSP. 3. Third-party cookies: If the Ory authentication process relies on third-party cookies, Edge's default settings might be blocking these, causing the login issues. 4. FedCM (Federated Credential Management) support: According to the [FedCM browser support documentation](https://www.ory.sh/docs/kratos/social-signin/fedcm#browser-support), Edge does support FedCM. If your setup is using this feature, there might be an interaction issue specific to Edge's implementation. To troubleshoot this issue: 1. Try clearing your browser cache and cookies in Edge. 2. Temporarily disable any browser extensions in Edge that might interfere with the authentication process. 3. Check if there are any updates available for your Edge browser. 4. If possible, try using Edge in InPrivate mode to see if the issue persists. If none of these steps resolve the issue, it would be best to contact Ory support directly with specific details about your setup and the exact error messages you're seeing in Edge. They would be better equipped to help with browser-specific issues that aren't covered in the general documentation.