Skip to content

help request: openid-connect plugin server-side session storage configuration #6792

Description

@mehmetcuneyit

Description

I see that lua-resty-openidc does the heavy-lifting. I would like to monitor/manage the session cache, and also use another server-side storage mechanisms other than shared-memory(default), e.g. memcache or redis. I'm worried about the shared-memory performance for large number of user sessions(1M+) even after proper scaling.

  • How can I configure APISIX to use redis as the session storage ?
  • Do I need to scale APISIX gateway to manage large number of sessions ?
  • What would you suggest about managing APISIX session storage in multi-cluster environment?
  • Overall, what would you suggest about session storage for the production as best practice ?

Any opinion would be appreciated 🙏

Environment

  • APISIX version (run apisix version): 2.13.0
  • Operating system (run uname -a):
  • OpenResty / Nginx version (run openresty -V or nginx -V):
  • etcd version, if relevant (run curl http://127.0.0.1:9090/v1/server_info):
  • APISIX Dashboard version, if relevant:
  • Plugin runner version, for issues related to plugin runners:
  • LuaRocks version, for installation issues (run luarocks --version):

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions