@@ -115,7 +115,7 @@ valid. If not specified, the token is considered active if the `active_attribute
115115
116116---
117117
118- ### jwt_key_id_template _ <template >_
118+ ### jwt_key_id_template _ <template\ >_
119119Default: ` {kid} `
120120
121121The template used to determine the key for ` jwt_key_table ` lookup. The template can include placeholders
@@ -124,7 +124,7 @@ replaced with `default`.
124124
125125---
126126
127- ### jwt_key_table _ <table >_
127+ ### jwt_key_table _ <table\ >_
128128Default: (none)
129129
130130The table to use for looking up the key to validate JWT tokens. The lookup key is determined by applying
@@ -135,7 +135,7 @@ all also implement the `table` interface.
135135
136136---
137137
138- ### jwt_valid_methods _ <method >_
138+ ### jwt_valid_methods _ <method\ >_
139139Default: all supported methods.
140140
141141The allowed signing algorithms for JWT tokens. If specified, the token's ` alg ` header field must match
@@ -145,14 +145,14 @@ It is not possible to enable `none` algorithm for JWT tokens.
145145
146146---
147147
148- ### jwt_issuers _ <issuer >_
148+ ### jwt_issuers _ <issuer\ >_
149149Default: (none)
150150
151151If specified, the token's ` iss ` claim must match one of these values to be considered valid.
152152
153153---
154154
155- ### jwt_expiry_leeway _ <duration >_
155+ ### jwt_expiry_leeway _ <duration\ >_
156156Default: 30s
157157
158158The leeway to apply when validating the token's ` exp ` claim. This allows for some clock skew between the
@@ -161,7 +161,7 @@ before `exp` + `jwt_expiry_leeway`.
161161
162162---
163163
164- ### jwt_audience _ <table >_
164+ ### jwt_audience _ <table\ >_
165165Default: (none)
166166
167167If specified, the token's ` aud ` claim must match one of the values in this table to be considered
0 commit comments