[MIR] libapache2-mod-auth-openidc

[Corey Bryant]

[Availability]
Currently in universe

[Rationale]
Keystone is an OpenStack project that we're aready support in main.
apache2 is also in main. libapache2-mod-auth-openidc will be used
in conjunction with keystone and apache2 to provide federated
authorization/authentication.

[Security]
https://ubuntu.com/security/cves?q=&package=libapache2-mod-auth-openidc&priority=&version=&status=
It appears these are all patched in the version that is in jammy.

[Quality Assurance]
Package works out of the box with no prompting. There are no major bugs
in Ubuntu and there are no major bugs in Debian. Tests are run during
build.

[Dependencies]
All are in main

[Standards Compliance]
FHS and Debian Policy compliant

[Maintenance]
Package that the OpenStack Team will take care of

[Background]
The libapache2-mod-auth-openidc package provides the mod_auth_openidc
authentication/authorization module for Apache2. It enables an Apache2
web server to operate as an OpenID Connect Relying Party towards an
OpenID Connect Provider, relaying user authentication to a provider
nad receiving user identity information from that provider, then
passes that identity information on to applications protected by the
Apache web server and establishes an authentication session for the
identified user.

The current use case for libapache2-mod-auth-openidc will be for
OpenStack Keystone federation. This allows users to authenticate
directly with another identity source and then provide keystone with
a set of user attributes, useful for organizations that already have
a primary identity source, preventing the need for a separate set of
cloud credentials.

[Lukas Märdian (slyon)]

Review for Package: src:libapache2-mod-auth-openidc
Author: @joalif
Reviewed-by: @slyon

[Summary]

libapache2-mod-auth-openidc provides the mod_auth_openidc
authentication/authorization module for Apache2.
This module enables an Apache 2.x web server to operate as an OpenID
Connect Relying Party (RP) towards an OpenID Connect Provider (OP).
It relays end user authentication to a Provider and receives user
identity information from that Provider. It then passes on that identity
information (a.k.a. claims) to applications protected by the Apache web
server and establishes an authentication session for the identified user.

MIR team ACK under the constraint to resolve the below listed
required TODOs and as much as possible having a look at the
recommended TODOs.

This does need a security review.

List of specific binary packages to be promoted to main: libapache2-mod-auth-openidc_2.4.10-1build1_amd64.deb

Notes:
- This package is security sensitive as it is exposed to the open web, being
  an apache2 module/plugin. It processes arbitrary URLs/web content as its input
- This package touches with two current transitions: prce2 and openssl3

Required TODOs:
- check runtime dependencies in universe (libcjose0, libhiredis0.14), they need
  to be dropped (if possible) or need a MIR as well
- drop the non functional autopkgtest (wrong indication of test coverage)
- enable symbols tracking for mod_auth_openidc.so
- build the package with pcre2:
  https://people.canonical.com/~ubuntu-archive/transitions/html/pcre3-to-pcre2.html
- check build-time warnings (especially about openssl3), if not critical mention
  it in this bug report; it can then be downgraded to a "recommended TODO" and
  fixed later. Otherwise, please resolve those issues.

Recommended TODOs:
- The package should get a team bug subscriber before being promoted
- a functional autopkgtest should be added
- Update to the latest upstream version 2.4.11 (still very new)
  https://github.com/zmartzone/mod_auth_openidc/releases

[Duplication]
- There is no other package in main providing the same functionality.

[Dependencies]
OK:
- no -dev/-debug/-doc packages that need exclusion
- No dependencies in main that are only superficially tested requiring
   more tests now.

Problems:
- Other runtime dependencies in universe, need MIR:
  - libcjose0 (>= 0.4.1)
  - libhiredis0.14 (0.14.1-2)

[Embedded sources and static linking]
OK:
- no embedded source present
- no static linking
- does not have odd Built-Using entries
- not a go package, no extra constraints to consider in that regard
- No vendoring used, all Built-Using are in main

Problems: None

[Security]
OK:
- history of CVEs does not look concerning
- does not run a daemon as root
- does not use webkit1,2
- does not use lib*v8 directly
- does not open a port/socket
- does not use centralized online accounts
- does not integrate arbitrary javascript into the desktop
- does not deal with security attestation (secure boot, tpm, signatures)

Problems:
- does parse data formats
- does deal with system authentication (eg, pam), etc)
- does process arbitrary web content (bearer/authentication tokens)

[Common blockers]
OK:
- does not FTBFS c...

[Christian Ehrhardt  (paelzer)]

There has been not further update for too long, for now we consider it invalid.
Feel free to re-open if there is effort backing it up and motivation to bring it to main.