Caching the result of .well-known/openid-configuration
Open
Nobody has claimed this yet.
Type: Feature
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Please add more information to the documentation so that we know if dataverse caches the result of well-known/openid-configuration for some time or not.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no documentation file or test. Start by locating the existing Dataverse documentation for .well-known/openid-configuration and verify whether its caching behavior is described. Done means the documentation clearly states whether Dataverse caches the result and, if so, for how long.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100