vigiloauth/vigilo

Support Request parameter during client authorization

Open

#346 opened on May 27, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Go (9 forks)auto 404
good first issuepriority: medium

Repository metrics

Stars
 (100 stars)
PR merge metrics
 (PR metrics pending)

Description

Description Add support for the OAuth 2.0/OpenID Connect request parameter, allowing clients to send a JWT-encoded request object directly in the authorization request. This enhances security by enabling signed and encrypted requests.

User Story: As a client developer, I want to send a signed JWT request object using the request parameter during authorization, So that I can securely transmit complex authorization request data.

Acceptance Criteria:

  • Support receiving the request parameter containing a JWT request object.
  • Validate the JWT signature and claims.
  • Parse and apply request object parameters to the authorization flow.
  • Handle errors for invalid or malformed request objects.
  • Document the feature and provide examples.

Contributor guide

Research direction
Examine the existing authorization endpoint implementation, specifically how request parameters are parsed. Add support for the 'request' parameter: parse the JWT, validate its signature using the client's registered JWKS or public key, extract and apply the contained claims. Ensure error handling for invalid JWTs.
Tech stack
go
Domain
backendsecurity
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitGoOAuth2JWT
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65