You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Support reading / writing / removing suffixed/un-suffixed cookies from `@clerk/clerk-js` and `@clerk/backend`.
8
+
The `__session`, `__clerk_db_jwt` and `__client_uat` cookies will now include a suffix derived from the instance's publishakeKey. The cookie name suffixes are used to prevent cookie collisions, effectively enabling support for multiple Clerk applications running on the same domain.
Copy file name to clipboardExpand all lines: integration/README.md
+4
Original file line number
Diff line number
Diff line change
@@ -577,6 +577,10 @@ This is why you created the `.keys.json` file in the [initial setup](#initial-se
577
577
578
578
They keys defined in `.keys.json.sample` correspond with the Clerk instances in the **Integration testing** organization.
579
579
580
+
### Test isolation
581
+
582
+
Before writing tests, it's important to understand how Playwright handles test isolation. Refer to the [Playwright documentation](https://playwright.dev/docs/browser-contexts) for more details.
583
+
580
584
> [!NOTE]
581
585
> The test suite also uses these environment variables to run some tests:
Some of our e2e test suites require self-signed SSL certificates to be installed on the local machine. This short guide will walk you through the process of generating self-signed SSL certificates using `mkcert`.
4
+
5
+
### Prerequisites
6
+
7
+
Good news! If you've set up your local development environment for Clerk, you've already installed `mkcert` as part of our `make deps` command. If you haven't, you can install it by following the instructions [here](https://github.com/FiloSottile/mkcert)
8
+
9
+
### Generate SSL Certificates
10
+
11
+
To generate a new cert/key pair, you can simply run the following command:
The command above will create a `example.pem` and a `example-key.pem` file in the current directory. The certificate will be valid for `example.com` and all subdomains of `example.com`.
18
+
19
+
### Using the Certificates
20
+
21
+
During installation, `mkcert` automatically adds its root CA to your machine's trust store. All certificates generated by `mkcert` from that point on, will you that specific root CA. This means that you can use the generated certificates in your local development environment without any additional configuration. There's an important caveat though: `node` does not use the system root store, so it won't accept mkcert certificates automatically. Instead, you will have to set the `NODE_EXTRA_CA_CERTS` environment variable.
For more details, see [here](https://github.com/FiloSottile/mkcert?tab=readme-ov-file#changing-the-location-of-the-ca-files)
34
+
35
+
### Github actions
36
+
37
+
In order to avoid install mkcert and generating self-signed certificates in our CI/CD pipeline, we have added the generated certificates and the root CA to the repository's secrets:
38
+
39
+
```shell
40
+
secrets.INTEGRATION_ROOT_CA
41
+
secrets.INTEGRATION_CERTS
42
+
```
43
+
44
+
During the CICD run, the certificates are loaded from the ENV and written to the `ingration/certs` directory.
0 commit comments