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: docs/en/latest/plugins/hmac-auth.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,9 +54,10 @@ The following attributes are available for configurations on Routes or Services.
54
54
| allowed_algorithms | array[string]| False |["hmac-sha1","hmac-sha256","hmac-sha512"]| combination of "hmac-sha1","hmac-sha256",and "hmac-sha512" | The list of HMAC algorithms allowed. |
55
55
| clock_skew | integer | False | 300 | >=1 | Maximum allowable time difference in seconds between the client request's timestamp and APISIX server's current time. This helps account for discrepancies in time synchronization between the client’s and server’s clocks and protect against replay attacks. The timestamp in the Date header (must be in GMT format) will be used for the calculation. |
56
56
| signed_headers | array[string]| False ||| The list of HMAC-signed headers that should be included in the client request's HMAC signature. |
57
-
| validate_request_body | boolean | False | false || If true, validate the integrity of the request body to ensure it has not been tampered with during transmission. Specifically, the Plugin creates a SHA-256 base64-encoded digest and compare it to the `Digest` header. If the Digest` header is missing or if the digests do not match, the validation fails. |
57
+
| validate_request_body | boolean | False | false || If true, validate the integrity of the request body to ensure it has not been tampered with during transmission. Specifically, the Plugin creates a SHA-256 base64-encoded digest and compare it to the `Digest` header. If the `Digest` header is missing or if the digests do not match, the validation fails. |
58
58
| hide_credentials | boolean | False | false || If true, do not pass the authorization request header to Upstream services. |
59
59
| anonymous_consumer | string | False ||| Anonymous Consumer name. If configured, allow anonymous users to bypass the authentication. |
60
+
| realm | string | False | hmac || The realm to include in the `WWW-Authenticate` header when authentication fails. |
60
61
61
62
NOTE: `encrypt_fields = {"secret_key"}` is also defined in the schema, which means that the field will be stored encrypted in etcd. See [encrypted storage fields](../plugin-develop.md#encrypted-storage-fields).
Copy file name to clipboardExpand all lines: docs/en/latest/plugins/jwt-auth.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -68,6 +68,7 @@ For Routes or Services:
68
68
| key_claim_name | string | False | key | The name of the JWT claim that contains the user key (corresponds to Consumer's key attribute). |
69
69
| anonymous_consumer | string | False | false | Anonymous Consumer name. If configured, allow anonymous users to bypass the authentication. |
70
70
| store_in_ctx | boolean | False | false | Set to true will store the JWT payload in the request context (`ctx.jwt_auth_payload`). This allows lower-priority plugins that run afterwards on the same request to retrieve and use the JWT token. |
71
+
| realm | string | False | jwt | The realm to include in the `WWW-Authenticate` header when authentication fails. |
71
72
72
73
You can implement `jwt-auth` with [HashiCorp Vault](https://www.vaultproject.io/) to store and fetch secrets and RSA keys pairs from its [encrypted KV engine](https://developer.hashicorp.com/vault/docs/secrets/kv) using the [APISIX Secret](../terminology/secret.md) resource.
0 commit comments