Describe the feature

Ideally the documentation should mention all the datastore models required by the OpenID Connect flows. The current documentation has this section for OAuth2.0 (https://oauthlib.readthedocs.io/en/latest/oauth2/server.html#create-your-datastore-models) but it is missing for OIDC.

We currently have the TOTP implementation nevertheless it would be nice to have a SMS / Text Message 2FA provider implementation that works as example implementation with some well known provider free development version.

Hi! There is a documented feature: you can fetch invoices by its status, even multiple statuses, what looks quite convenient. Is this supported now? Cannot find this option in Type Script definitions.
Thanks!

I use 3.0.21.

https://developer.xero.com/documentation/api/invoices

when I use the vue, the redirect_uri is a http address like this: http://localhost:8080/signin, but when in Electron app, this address not valid because there isn't a http server exist, so which is the substitude for that address?

The documentation mention the oauth_body_hash should be encoded Base64.

https://tools.ietf.org/id/draft-eaton-oauth-bodyhash-00.html#parameter
But also reading the doc example, the final string oauth_body_hash should be uri encoded like baseString and oauth_signature.

Base64 encoded SHA-1 hash of the body:

Lve95gjOVATpfV8EL5X4nxwjKHE=

Header: 
` PUT /resource HTTP/1.1
  H

New provider implementations are welcome! 👋