EUDI needs without a Keycloak issue
How relevance is rated
- Blocker
- Keycloak can't be used for production EUDI without it.
- High
- Required by regulation or HAIP, needed by most deployments, or a real security issue.
- Medium
- Improves EUDI flows or is needed by some deployments.
- Low
- Admin UI, docs, tests, refactoring, or formats EUDI doesn't use.
- None
- Touches OpenID4VC code but not EUDI use.
The basis says why an item matters.
- Legal
- An implementing regulation, or an ARF or ETSI requirement it relies on.
- Profile
- HAIP or the OpenID4VC specs, needed to work with EUDI wallets.
- Usable
- No rule asks for it, but real deployments can't do without it. One example is the German PID, which has no stable identifier.
- Security
- Fixes a weakness.
- Hygiene
- Cleanup, UI, docs or tests.
Open items were rated by hand and checked by three independent reviews against the sources below. Finished items are rated by topic only.
| # | Title | State | Relevance | Review | PR size | Updated |
|---|
Nothing matches these filters.