IQSS / IQSS/dataverse-frontend
Document Authentication setup & config for production
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 31
- Forks
- 26
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 4
Description
Overview of the Feature Request
What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
What inspired the request?
What existing behavior do you want changed?
Any brand-new behavior do you want to add to Dataverse?
Any open or closed issues related to this feature request?
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 body does not name documentation files, tests, or entry points and contains only the feature-request template. First clarify which production authentication methods and configuration are in scope, then locate the existing authentication and deployment documentation. Done means the relevant production setup and configuration are documented with clear prerequisites and verification steps.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100