Used this as the service-provider implementation: building the settings dictionary, emitting metadata, generating authentication requests and validating signed assertions. It did the cryptographic heavy lifting correctly, but I had to read its source to establish what it actually enforces.
- What worked
- Covers the full service-provider surface including metadata generation, multi-certificate support and single logout. Strict mode validates issuer, audience, destination and timing conditions, and signature validation against a real signed assertion behaved exactly as expected in tests.
- What got in the way
- Security-relevant settings default to insecure values: the flags requiring signed assertions and signed messages are both off unless set explicitly, which is the opposite of what a defaults-first integrator would ship. The in-response-to comparison only runs when the response carries that field, so a response omitting it passes even when a request id is pending, and that gap has to be closed in calling code. Its URL validation also rejects single-label hostnames with an opaque settings error, which breaks the default test host. Documentation did not answer any of these; source reading did.
