StubID
A stand-in for the Danish MitID identity brokers' test environments, so an integration that signs users in with MitID can be tested without one.
What it emulates is checked byte for byte against recordings of the real broker, including the parts that look like mistakes. Where it knowingly differs it says so, in the ledger a running instance serves and in the divergences.
Start here
The shortest path from nothing to a page of claims is signing in. It
routes you to whichever of the four client stacks is yours, and it starts with a docker run line
you can paste.
Running it from a test suite
| From a test suite | StubId.Testing, which starts a container and hands the address to the application under test |
| Inside the test process | StubId.InProcess, which needs no Docker at all |
| Deciding what a login does | how an outcome is chosen, why it was what it was, and what a timeout looks like |
| Watching an instance | the pages every instance serves, and why there is no password on them |
| Trusting the certificate | per stack, when an instance serves TLS |
| Driving a real browser | Chromium, Firefox and WebKit, which the real broker makes impossible |
What the broker actually does
Written from recordings rather than from the vendor's documentation, because the two disagreed often and the recording won every time. The broker reference has the tokens, the refusals, the request parameters, and every place StubID differs on purpose.
Why things are the way they are
CPR numbers and test data explains why the personal numbers here belong to nobody by construction. The profile seam explains what is behind the broker abstraction and what deliberately is not yet.
The capture session is the runbook for taking a new recording.
The API
The reference covers the four packages a reader installs: StubId.Client,
StubId.Testing, StubId.InProcess and StubId.Abstractions.
Where it is
What stays compatible says what a suite can rely on, what will move, and what happens before it moves. The roadmap says what is done and what is not. The releases say what changed, and the version is a date for the reason the first one gives.
StubID is not affiliated with, endorsed by, or connected to Nets, Signaturgruppen, Digitaliseringsstyrelsen or MitID A/S. It emulates a published protocol surface for testing.