nic-6443 opened a new pull request, #13496:
URL: https://github.com/apache/apisix/pull/13496

   ### Description
   
   Follow-up to #13178, which added the flat lua-resty-session session options 
(`cookie_name`, `cookie_path`, `cookie_secure`, `*_timeout`, …) and the 
`cookie.lifetime` → `absolute_timeout` compatibility mapping. That PR's tests 
covered schema validation and the `build_session_opts` transform, but nothing 
exercised the options at runtime.
   
   This adds two integration tests to `t/plugin/openid-connect.t` that run the 
full Keycloak Relying Party login flow and assert real behavior:
   
   - **custom `session.cookie_name`** — the session cookie issued after login 
uses the configured name instead of the default `session`, and the renamed 
cookie is a working session (protected URI returns 200). Covers the use case 
from #13031.
   - **`session.absolute_timeout`** — after the configured timeout elapses, the 
session is rejected and the request is redirected back to the IdP for 
re-authentication, proving the timeout actually takes effect. Covers the 
regression in #13177.
   
   Both tests fail against a build where the flat options are dropped before 
reaching `resty.session` (verified locally: the cookie falls back to `session=` 
and the session no longer expires), so they guard the pass-through, not just 
the schema.
   
   ### Which issue(s) this PR fixes:
   
   Related to #13031 and #13177; follow-up to #13178.
   
   ### Checklist
   
   - [x] I have explained the need for this PR and the problem it solves
   - [x] I have explained the changes or the new features added to this PR
   - [x] I have added tests corresponding to this change
   - [x] I have updated the documentation to reflect this change
   - [x] I have verified that this change is backward compatible (If not, 
please discuss on the [APISIX mailing 
list](https://github.com/apache/apisix/tree/master#community) first)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to