OpenAPI: default values for Client's lifetimes are misleading
Following #211 and #194, we found out that, by default, OpenAPI sets default values for authorization_code_lifetime_seconds, access_id_token_lifetime_seconds and refresh_token_lifetime_seconds to 0.
This is misleading because, as we've seen, developers can copy/paste the whole example payload and inadvertently set the token lifetime to zero.
We should tweak the Pydantic schema so OpenAPI shows more sensible values.
BTW, maybe we should reconsider the minimum validation for those values, which is currently 0.
How does funding with Polar work?
Pay now to fund the work behind this issue.
Get updates on progress being made.
Maintainer is rewarded once the issue is completed.
Backer
You're funding impactful open source efforts
Contributor
You want to contribute to this effort
Maintainer
You want to get funding like this too