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
- change `KEYCLOAK_ADMIN` and `KEYCLOAK_ADMIN_PASSWORD` to your own values.
38
-
-`NEXTAUTH_SECRET`: is NextAuth internal for JWT encryption and easily created with command `openssl rand -base64 32`.
39
-
-`NEXTAUTH_URL`: should be the base url to the auth page: `${FRONTEND_URL}/api/auth`.
40
-
-`NEXTAUTH_ID`: name of the provider which is shown in the `Sign in with {NEXTAUTH_ID}`, default is `keycloak`.
41
-
- run `docker compose up -d` to start keycloak.
42
-
- log into keycloak at http://localhost:8085
43
-
- keycloak setup (use the `apps/{folder}` env):
44
-
- follow the [keycloak docs](https://www.keycloak.org/getting-started/getting-started-docker#_secure_the_first_application) to create a new realm and at least one user.
45
-
- after creating the realm, copy paste the url of the realm `http://{YOUR_KEYCLOAK_DOMAIN}/realms/{YOUR_REALM}` in your env as variable `NEXTAUTH_ISSUER`.
46
-
- Create a client.
47
-
- first page: fill in a name for `ClientID`. (`.env.example` default is `orchestrator-client`)
48
-
- second page: enable `Client authentication` and `Authorization`.
49
-
- third page fill in `Valid redirect URIs` and `Web Origins`:
50
-
-`Valid redirect URIs` with `{FRONTEND_URL}/api/auth/callback/{PROVIDER}`, with default provider its env variable `NEXTAUTH_ID`. (eg `http://localhost:3000/api/auth/callback/keycloak`)
51
-
-`Web Origins` with `{FRONTEND_URL}`. (eg `http://localhost:3000/`)
52
-
- go to the client details and go to tab `Credentials` and copy the Client secret and paste it into your env file. (`NEXTAUTH_CLIENT_SECRET`)
53
-
- run the app with `turbo dev`.
54
-
- keycloak backend setup:
55
-
- Create another client in the same realm.
56
-
- first page: fill in a name for `ClientID`. (set the client id in your env (`OAUTH2_RESOURCE_SERVER_ID`)).
57
-
- second page: enable `Client authentication` and `Authorization`.
58
-
- third page: does not need any config.
59
-
- go to the client details and go to tab `Credentials` and copy the Client secret and pase it into your env file. (`OAUTH2_RESOURCE_SERVER_SECRET`)
60
-
- if you don't use authorization and only use authentication set `OAUTH2_AUTHORIZATION_ACTIVE` to `False`. if you do have authentication, you should set `OAUTH2_TOKEN_URL` to the inspection endpoint of your auth provider.
-change `KEYCLOAK_ADMIN` and `KEYCLOAK_ADMIN_PASSWORD` to your own values.
38
+
-`NEXTAUTH_SECRET`: is NextAuth internal for JWT encryption and easily created with command `openssl rand -base64 32`.
39
+
-`NEXTAUTH_URL`: should be the base url to the auth page: `${FRONTEND_URL}/api/auth`.
40
+
-`NEXTAUTH_ID`: name of the provider which is shown in the `Sign in with {NEXTAUTH_ID}`, default is `keycloak`.
41
+
-run `docker compose up -d` to start keycloak.
42
+
-log into keycloak at http://localhost:8085
43
+
-keycloak setup (use the `apps/{folder}` env):
44
+
-follow the [keycloak docs](https://www.keycloak.org/getting-started/getting-started-docker#_secure_the_first_application) to create a new realm and at least one user.
45
+
-after creating the realm, copy paste the url of the realm `http://{YOUR_KEYCLOAK_DOMAIN}/realms/{YOUR_REALM}` in your env as variable `NEXTAUTH_ISSUER`.
46
+
-Create a client.
47
+
-first page: fill in a name for `ClientID`. (`.env.example` default is `orchestrator-client`)
48
+
-second page: enable `Client authentication` and `Authorization`.
49
+
-third page fill in `Valid redirect URIs` and `Web Origins`:
50
+
-`Valid redirect URIs` with `{FRONTEND_URL}/api/auth/callback/{PROVIDER}`, with default provider its env variable `NEXTAUTH_ID`. (eg `http://localhost:3000/api/auth/callback/keycloak`)
51
+
-`Web Origins` with `{FRONTEND_URL}`. (eg `http://localhost:3000/`)
52
+
-go to the client details and go to tab `Credentials` and copy the Client secret and paste it into your env file. (`NEXTAUTH_CLIENT_SECRET`)
53
+
-run the app with `turbo dev`.
54
+
-keycloak backend setup:
55
+
-Create another client in the same realm.
56
+
-first page: fill in a name for `ClientID`. (set the client id in your env (`OAUTH2_RESOURCE_SERVER_ID`)).
57
+
-second page: enable `Client authentication` and `Authorization`.
58
+
-third page: does not need any config.
59
+
-go to the client details and go to tab `Credentials` and copy the Client secret and pase it into your env file. (`OAUTH2_RESOURCE_SERVER_SECRET`)
60
+
-if you don't use authorization and only use authentication set `OAUTH2_AUTHORIZATION_ACTIVE` to `False`. if you do have authentication, you should set `OAUTH2_TOKEN_URL` to the inspection endpoint of your auth provider.
61
+
-run the backend.
62
62
63
63
# Contributing
64
64
@@ -72,11 +72,11 @@ Each PR, which typically addresses an existing ticket from the issue list, shoul
72
72
npm run packages:changeset
73
73
```
74
74
75
-
- Include the changes made by this command in pull requests to the main branch
76
-
- Selecting packages that will get a version bump
77
-
- Specifies per selected package the type of version bump (`major`, `minor` or `patch`)
78
-
- Adds a description or release notes for the release
79
-
- All entries will be saved in a `.md` file in the `.changeset` folder
75
+
-Include the changes made by this command in pull requests to the main branch
76
+
-Selecting packages that will get a version bump
77
+
-Specifies per selected package the type of version bump (`major`, `minor` or `patch`)
78
+
-Adds a description or release notes for the release
79
+
-All entries will be saved in a `.md` file in the `.changeset` folder
80
80
81
81
Once the pull-request with a changeset file is merged to the main branch another PR is opened by the Changesets-bot to update the version numbers of the packages. When this pull request gets merged to main an automatic publish to NPM will be performed.
0 commit comments