Sorry if I missed something - I did try to dig around, but I don't think there are any specific examples or other issues/discussions related to this.

I'm trying to implement a lightweight oidc provider. AFAIK that usage is within the scope of this crate - the readme has an example for the provider-side well-known endpoint data for instance, providing a struct the provider can return to clients.

I'm trying to parse the query parameters of the initial request to the authenticate endpoint (?redirect_url=abc,state=xyz,... probably with serde_urlencoded) and while there are types that correspond to this data (RequestUrl, or maybe AuthorizationRequest?) they're closed and tightly coupled with the client-side.

Could pure-data types maybe be split out and opened up, or maybe similar provider-side structs be provided? I'm not sure how best to handle it. Though I guess I'd prefer having a bunch of data structs but no help with the request flow than help for part of the request flow but not all the data structs.