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: content/en/library/authentication/index.md
+18-27Lines changed: 18 additions & 27 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title : "Authentication - JWT"
3
3
description: "Adds the integration with JWT using an available authentication middleware and system components to validate and grant the access tokens."
4
4
lead: ""
5
5
date: 2023-05-13T15:40:19+02:00
6
-
lastmod: 2023-06-25T15:40:19+02:00
6
+
lastmod: 2024-11-17T00:00:00+02:00
7
7
draft: false
8
8
images: []
9
9
menu:
@@ -32,13 +32,13 @@ There are three different ways you can to create the access tokens:
32
32
33
33
- Using a certificate.
34
34
- Using a secret key.
35
-
- Using a OpenId external provider.
35
+
- Using an OpenId external provider.
36
36
37
-
Using a certificate is the most secure way to create the access tokens. The certificate can be stored in the file system or in the Azure Key Vault.
37
+
**Using a certificate** is the most secure way to create the access tokens. The certificate can be stored in the file system or in the Azure Key Vault.
38
38
39
-
Using a secret key is the simplest way to create the access tokens. The secret key is stored in the appsettings.json file.
39
+
**Using a secret** key is the simplest way to create the access tokens. The secret key is stored in the appsettings.json file.
40
40
41
-
Using a OpenId external provider is the most flexible way to create the access tokens. The OpenId provider can be configured in the appsettings.json file.
41
+
**Using an OpenId external provider** is the most flexible way to create the access tokens. The OpenId provider can be configured in the `appsettings.json` file.
42
42
43
43
## JWT authentication with CERTIFICATE
44
44
@@ -161,31 +161,22 @@ To blacklist and deactivate the access tokens, use `IAccessTokenService` and inv
161
161
162
162
The default section name for the JWT settings is `jwt`. The following options are available:
163
163
164
-
`enabled` - If true then the JWT authentication is enabled.
165
-
166
-
`allowAnonymousEndpoints` - If true then the JWT authentication is disabled for the endpoints with the AllowAnonymous attribute.
167
-
168
-
`certificate` - Certificate used to issue or just validate the tokens (including private key or just the public one).
169
-
170
-
`algorithm` - The algorithm used to sign the tokens.
171
-
172
-
`issuer` - A party signing the tokens.
173
-
174
-
`secretKey` - A secret key used to create the access tokens (instead of using the certificate).
175
-
176
-
`expiry` - How long the token will remain valid.
177
-
178
-
`validateLifetime` - If true then the lifetime defined in expiryMinutes will be validated.
179
-
180
-
`validAudience` - An audience that can use the access tokens.
181
-
182
-
`validateAudience` - If true then the audience defined in validAudience will be validated.
164
+
-`enabled` - If true then the JWT authentication is enabled.
165
+
-`allowAnonymousEndpoints` - If true then the JWT authentication is disabled for the endpoints with the AllowAnonymous attribute.
166
+
-`certificate` - Certificate used to issue or just validate the tokens (including private key or just the public one).
167
+
-`algorithm` - The algorithm used to sign the tokens.
168
+
-`issuer` - A party signing the tokens.
169
+
-`secretKey` - A secret key used to create the access tokens (instead of using the certificate).
170
+
-`expiry` - How long the token will remain valid.
171
+
-`validateLifetime` - If true then the lifetime defined in expiryMinutes will be validated.
172
+
-`validAudience` - An audience that can use the access tokens.
173
+
-`validateAudience` - If true then the audience defined in validAudience will be validated.
183
174
184
175
## Settings
185
176
186
-
**appsettings.json**
177
+
Use the following settings in the `appsettings.json` file according to your needs
187
178
188
-
```json
179
+
```json
189
180
"jwt": {
190
181
"enabled": true,
191
182
"allowAnonymousEndpoints": [
@@ -241,7 +232,7 @@ The default section name for the JWT settings is `jwt`. The following options ar
241
232
242
233
Default settings for some variable has bee overwritten with the following configuration.
Copy file name to clipboardExpand all lines: content/en/library/azure-key-vault/index.md
+12-14Lines changed: 12 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,6 +3,7 @@ title : "Azure Key Vault"
3
3
description: "Genocs Library package for Azure Key Vault"
4
4
lead: ""
5
5
date: 2023-11-29T21:00:19+02:00
6
+
lastmod: 2024-11-17T00:00:00+02:00
6
7
draft: false
7
8
images: []
8
9
menu:
@@ -58,25 +59,22 @@ builder.Host
58
59
59
60
### Options
60
61
61
-
`enabled` - Enable or disable the Azure Key Vault configuration. Default is false
62
+
-`enabled` - Enable or disable the Azure Key Vault configuration. Default is false
63
+
-`name` - Sets the key vault name to be used. If the key vault url is `https://kyvault.vault.azure.net/` then the name is `kyvault`.
64
+
-`managedIdentityId` - Sets the managed identity id to be used. You can find the managed identity id in the Azure portal. The managed identity id is the object id of the managed identity.
65
+
-`azureADCertThumbprint` - The client id. To be used with *Certificate authentication*.
66
+
-`azureADApplicationId` - The Active Directory Application id. To be used with *Certificate authentication*.
67
+
-`azureADDirectoryId` - The Azure EntraID tenant Id. To be used with *Certificate authentication*.
62
68
63
-
`name` - Sets the key vault name to be used. If the key vault url is `https://kyvault.vault.azure.net/` then the name is `kyvault`.
64
69
65
-
`managedIdentityId` - Sets the managed identity id to be used. You can find the managed identity id in the Azure portal. The managed identity id is the object id of the managed identity.
70
+
> **NOTE:**
71
+
>
72
+
> In case of RBAC, you don't need to set the managed identity id.
66
73
67
-
`azureADCertThumbprint` - The client id. To be used with Certificate authentication.
68
74
69
-
`azureADApplicationId` - The Active Directory Application id. To be used with Certificate authentication.
75
+
Use the following settings in the `appsettings.json` file according to your needs
70
76
71
-
`azureADDirectoryId` - The Azure EntraID tenant Id. To be used with Certificate authentication.
72
-
73
-
74
-
**NOTE:** In case of RBAC, you don't need to set the managed identity id.
0 commit comments