Thu, 09 Mar 2023 13:15:13 +0100 mod_http_oauth2: Close site header tags
Kim Alvefur <zash@zash.se> [Thu, 09 Mar 2023 13:15:13 +0100] rev 5231
mod_http_oauth2: Close site header tags
Tue, 07 Mar 2023 23:55:33 +0100 mod_http_oauth2: Fix contrast of links on consent page
Kim Alvefur <zash@zash.se> [Tue, 07 Mar 2023 23:55:33 +0100] rev 5230
mod_http_oauth2: Fix contrast of links on consent page The default dark blue wasn't very visible on a dark background
Tue, 07 Mar 2023 15:33:07 +0000 mod_http_oauth2: token endpoint: handle missing credentials
Matthew Wild <mwild1@gmail.com> [Tue, 07 Mar 2023 15:33:07 +0000] rev 5229
mod_http_oauth2: token endpoint: handle missing credentials
Tue, 07 Mar 2023 15:31:19 +0000 mod_http_oauth2: Fail early when no authorization header present
Matthew Wild <mwild1@gmail.com> [Tue, 07 Mar 2023 15:31:19 +0000] rev 5228
mod_http_oauth2: Fail early when no authorization header present Fixes traceback.
Tue, 07 Mar 2023 15:27:50 +0000 mod_http_oauth2: Support HTTP Basic auth on token endpoint
Matthew Wild <mwild1@gmail.com> [Tue, 07 Mar 2023 15:27:50 +0000] rev 5227
mod_http_oauth2: Support HTTP Basic auth on token endpoint This is described in RFC 6749 section 2.3.1 and draft-ietf-oauth-v2-1-07 2.3.1 as the recommended way to transmit the client's credentials. The older spec even calls it the "client password", but the new spec clarifies that this is just another term for the client secret.
Tue, 07 Mar 2023 15:18:41 +0000 mod_http_oauth2: Separate extracting credentials from requests and verifying
Matthew Wild <mwild1@gmail.com> [Tue, 07 Mar 2023 15:18:41 +0000] rev 5226
mod_http_oauth2: Separate extracting credentials from requests and verifying The token endpoint also uses Basic auth, but the password would be the client_secret, so we need to verify against that instead of using test_password(). Splitting this up here avoids code duplication. Possibly this new function could go into util.http...
Tue, 07 Mar 2023 14:52:43 +0000 mod_http_oauth2: Reflect ALL attributes of the client registration
Matthew Wild <mwild1@gmail.com> [Tue, 07 Mar 2023 14:52:43 +0000] rev 5225
mod_http_oauth2: Reflect ALL attributes of the client registration Per RFC 7591: " Additionally, the authorization server MUST return all registered metadata about this client, including any fields provisioned by the authorization server itself. " The idea is that the server may replace/drop fields in the registration, so what gets reflected back to the client is the source of truth about the registration.
Tue, 07 Mar 2023 14:59:45 +0100 mod_rest: Point URLs to mod_http_oauth2 in demo mode
Kim Alvefur <zash@zash.se> [Tue, 07 Mar 2023 14:59:45 +0100] rev 5224
mod_rest: Point URLs to mod_http_oauth2 in demo mode
Tue, 07 Mar 2023 13:19:19 +0000 mod_http_oauth2: Improve handling of redirect_uri matching and fallback
Matthew Wild <mwild1@gmail.com> [Tue, 07 Mar 2023 13:19:19 +0000] rev 5223
mod_http_oauth2: Improve handling of redirect_uri matching and fallback Per OAuth 2.1, the client MUST provide a redirect_uri explicitly if it registered multiple. If it only registered a single URI, it may be omitted from the authorize request.
Tue, 07 Mar 2023 13:14:25 +0100 mod_http_oauth2: Correct field name for HTTP response status code
Kim Alvefur <zash@zash.se> [Tue, 07 Mar 2023 13:14:25 +0100] rev 5222
mod_http_oauth2: Correct field name for HTTP response status code 'code' is used in the incoming side of the Prosody HTTP stack while 'status_code' is used on the response side. Not confusing at all. The default is 200 so this mistake had no real effect.
(0) -3000 -1000 -300 -100 -10 +10 +100 +300 tip