OpenConext / OpenConext/OpenConext-manage
Feature request: warn about duplicate certData values
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 7
- Forks
- 13
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 7
Description
I just ran into the situation where we had made a mistake during an IdP key-rollover and we accidentally put the old key in both certData and certData2 instead of putting the new key in certData2.
This made me wonder if we could get a trigger warning if any of the certData values are the same.
An indicator that marks expired and nearly expired keys would also be really nice to have and would probably also have prevented our mistake.
Contributor guide
No contributing guide indexed for this repository
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 tracing how certData and certData2 are stored, validated, and presented in OpenConext-manage. Clarify whether the requested result includes duplicate-value warnings, expired-key indicators, nearly expired-key indicators, or all three, then define completion criteria and tests for each behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100