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
Copy file name to clipboardExpand all lines: README.md
+6-8Lines changed: 6 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,11 +51,11 @@ For a private client (ie a client that runs within the frontend, such as single
51
51
52
52
The generated client secret will be stored in AWS Secrets Manager in the same account & region as the deployment. The name of this secret will follow the following convention: `veda-keycloak-$stage-client-$clientId`(eg a Grafana client in the production deployment will generate the following secret: `veda-keycloak-prod-client-grafana`). The generated secret contains the following information:
53
53
54
-
* `id`: OAuth Client ID
55
-
* `secret`: OAuth Client Secret
56
-
* `auth_url`: URL of the OAuth [authorization endpoint](https://datatracker.ietf.org/doc/html/rfc6749#section-3.1)
57
-
* `token_url`: URL of the OAuth [token endpoint](https://datatracker.ietf.org/doc/html/rfc6749#section-3.2)
58
-
* `userinfo_url`: URL of the OIDC [user info endpoint](https://openid.net/specs/openid-connect-core-1_0.html#UserInfo)
54
+
-`id`: OAuth Client ID
55
+
-`secret`: OAuth Client Secret
56
+
-`auth_url`: URL of the OAuth [authorization endpoint](https://datatracker.ietf.org/doc/html/rfc6749#section-3.1)
57
+
-`token_url`: URL of the OAuth [token endpoint](https://datatracker.ietf.org/doc/html/rfc6749#section-3.2)
58
+
-`userinfo_url`: URL of the OIDC [user info endpoint](https://openid.net/specs/openid-connect-core-1_0.html#UserInfo)
59
59
60
60
A minimum example of a private client (note `publicClient: false` and `secret`):
61
61
@@ -78,7 +78,6 @@ clients:
78
78
79
79
<summary>Consider also using an environment variable for URLs for greater flexibility</summary>
80
80
81
-
82
81
```yaml
83
82
clients:
84
83
- clientId: grafana
@@ -458,14 +457,13 @@ VEDA Keycloak includes a custom `EmailSenderProvider` based on Keycloak’s `Def
458
457
> [!TIP]
459
458
> See the Service Provider Interfaces section in the [Server Developer Guide](https://www.keycloak.org/docs/latest/server_development/#_providers) for more details about how to create custom themes.
460
459
461
-
462
-
463
460
### Themes
464
461
465
462
> [!TIP]
466
463
> See the theme section in the [Server Developer Guide](https://www.keycloak.org/docs/latest/server_development/#_themes) for more details about how to create custom themes.
467
464
468
465
### SES Relay
466
+
469
467
The AWS account that includes the SES `openveda.cloud` identity does not permit creating SMTP credentials for AWS SES for security reasons. However, Keycloak expects to talk to an SMTP server for sending transactional emails such as verification, password reset, and notification messages.
470
468
471
469
To bridge this gap, we deploy a small SMTP relay service as an ECS Fargate service into the same VPC as Keycloak:
0 commit comments