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/openid-connect.md
+5-11Lines changed: 5 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,7 +64,7 @@ The `openid-connect` Plugin supports the integration with [OpenID Connect (OIDC)
64
64
| set_userinfo_header | boolean | False | true || If true and if user info data is available, set the value in the `X-Userinfo` request header. |
65
65
| set_refresh_token_header | boolean | False | false || If true and if the refresh token is available, set the value in the `X-Refresh-Token` request header. |
66
66
| session | object | False ||| Session configuration used when `bearer_only` is `false` and the Plugin uses Authorization Code flow. |
67
-
| session.secret | string | True || 16 or more characters | Key used for session encryption and HMAC operation when `bearer_only` is `false`. It is automatically generated and saved to etcd if not configured. When using APISIX in the standalone mode where etcd is no longer the configuration center, the `secret` should be configured. |
67
+
| session.secret | string | True || 16 or more characters | Key used for session encryption and HMAC operation when `bearer_only` is `false`. |
| session_contents | object | False ||| Session content configurations. If unconfigured, all data will be stored in the session. |
@@ -231,17 +231,11 @@ To properly configure the redirection URI, make sure that the `redirect_uri` mat
231
231
232
232
You should also ensure that the `redirect_uri` include the scheme, such as `http` or `https`.
233
233
234
-
#### 2. Missing Session Secret
235
-
236
-
If you deploy APISIX in the [standalone mode](/apisix/production/deployment-modes#standalone-mode), make sure that `session.secret` is configured.
237
-
238
-
User sessions are stored in browser as cookies and encrypted with session secret. The secret is automatically generated and saved to etcd if no secret is configured through the `session.secret` attribute. However, in standalone mode, etcd is no longer the configuration center. Therefore, you should explicitly configure `session.secret` for this Plugin in the YAML configuration center `apisix.yaml`.
239
-
240
-
#### 3. Cookie Not Sent or Absent
234
+
#### 2. Cookie Not Sent or Absent
241
235
242
236
Check if the [`SameSite`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie#samesitesamesite-value) cookie attribute is properly set (i.e. if your application needs to send the cookie cross sites) to see if this could be a factor that prevents the cookie being saved to the browser's cookie jar or being sent from the browser.
243
237
244
-
#### 4. Upstream Sent Too Big Header
238
+
#### 3. Upstream Sent Too Big Header
245
239
246
240
If you have NGINX sitting in front of APISIX to proxy client traffic, see if you observe the following error in NGINX's `error.log`:
247
241
@@ -253,11 +247,11 @@ If so, try adjusting `proxy_buffers`, `proxy_buffer_size`, and `proxy_busy_buffe
253
247
254
248
Another option is to configure the `session_content` attribute to adjust which data to store in session. For instance, you can set `session_content.access_token` to `true`.
255
249
256
-
#### 5. Invalid Client Secret
250
+
#### 4. Invalid Client Secret
257
251
258
252
Verify if `client_secret` is valid and correct. An invalid `client_secret` would lead to an authentication failure and no token shall be returned and stored in session.
259
253
260
-
#### 6. PKCE IdP Configuration
254
+
#### 5. PKCE IdP Configuration
261
255
262
256
If you are enabling PKCE with the authorization code flow, make sure you have configured the IdP client to use PKCE. For example, in Keycloak, you should configure the PKCE challenge method in the client's advanced settings:
0 commit comments