nixsearch / pkg / lua54Packages.lua-resty-openidc

lua54Packages.lua-resty-openidc

A library for NGINX implementing the OpenID Connect Relying Party (RP) and the OAuth 2.0 Resource Server (RS) functionality

Apache-2.0 github.com lua54Packages.lua-resty-openidc 5 releases newest changed 16 days ago

version1.9.1-1 attributelua54Packages.lua-resty-openidc rev419fe0f449b3fbe3bdd53d9840288db4509ec32e 2026-09-28 · one commit for every system systems✓ aarch64-darwin✓ aarch64-linuxx86_64-darwin✓ x86_64-linux

$ devbox add lua54Packages.lua-resty-openidc@1.9.1-1

$ nix shell github:NixOS/nixpkgs/419fe0f449b3fbe3bdd53d9840288db4509ec32e#lua54Packages.lua-resty-openidc

JSON: /v2/resolve?name=lua54Packages.lua-resty-openidc&version=latest

Releases

newest first, as /v2/pkg orders them

Version	arm mac	arm linux	x86 mac	x86 linux	Attribute	Commit	Date
1.9.1-1resolved	✓	✓	–	✓	`lua54Packages.lua-resty-openidc`	02f5696b0e	2026-09-13
1.9.0-1	✓	✓	✓	✓	`lua54Packages.lua-resty-openidc`	varies	2026-08-27
1.8.0-1	✓	✓	✓	✓	`lua54Packages.lua-resty-openidc`	3d46470bb3	2026-06-27
1.7.6-3	✓	✓	✓	✓	`lua54Packages.lua-resty-openidc`	a9858885e1	2024-06-12
1.7.5-1	✓	✓	✓	✓	`lua54Packages.lua-resty-openidc`	84e33aea0f	2023-02-26

Prereleases are listed but latest never picks one. “varies” means each system last changed at a different nixpkgs commit — the release page lists them.

Description

lua-resty-openidc is a library for NGINX implementing the OpenID Connect Relying Party (RP) and the OAuth 2.0 Resource Server (RS) functionality. When used as an OpenID Connect Relying Party it authenticates users against an OpenID Connect Provider using OpenID Connect Discovery and the Basic Client Profile (i.e. the Authorization Code flow). When used as an OAuth 2.0 Resource Server it can validate OAuth 2.0 Bearer Access Tokens against an Authorization Server or, in case a JSON Web Token is used for an Access Token, verification can happen against a pre-configured secret/key . It maintains sessions for authenticated users by leveraging lua-resty-session thus offering a configurable choice between storing the session state in a client-side browser cookie or use in of the server-side storage mechanisms shared-memory|memcache|redis. It supports server-wide caching of resolved Discovery documents and validated Access Tokens. It can be used as a reverse proxy terminating OAuth/OpenID Connect in front of an origin server so that the origin server/services can be protected with the relevant standards without implementing those on the server itself.