IQSS / IQSS/dataverse-frontend
Fix shib-dev-env
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
After the latest updates in Dataverse, Keycloak, and the SPI, shib-dev-env is not working. We need to update the environment to be compatible with the latest versions in the architecture.
Although it is not an environment used regularly, it is a use case of Shib configured directly as a SAML IdP provider in Keycloak, and it is useful to keep this example available for possible future scenarios that may seek to replicate it.
What kind of user is the feature intended for?
Sysadmin, developer
What inspired the request?
Failing shib-dev-env
What existing behavior do you want changed?
N/A
Any brand-new behavior do you want to add to Dataverse?
N/A
Any open or closed issues related to this feature request?
None
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
Start by locating the shib-dev-env configuration and reproducing its failure against the current Dataverse, Keycloak, and SPI versions. Trace the compatibility break across the SAML IdP setup; done means the environment runs again and preserves this example.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100