{"id":"soluto-oidc-server-mock","name":"oidc-server-mock","homepage":"https://hub.docker.com/r/soluto/oidc-server-mock","repo_url":"https://hub.docker.com/r/soluto/oidc-server-mock","category":"auth","subcategories":[],"tags":["oidc","oauth2","mock","identity","authentication","testing","devtools"],"what_it_does":"oidc-server-mock is a mock OpenID Connect (OIDC) provider/server intended to emulate OIDC flows for development and testing (e.g., for verifying login integrations without a real identity provider).","use_cases":["Integration testing of OIDC/OAuth2 client applications","Local development environments that need a fake identity provider","E2E testing of login/redirect/callback behavior","Validation of JWT/OIDC-related client logic and configuration"],"not_for":["Production identity/authorization use","Security-critical testing that requires production-grade threat modeling and hardening"],"best_when":"You need a lightweight, controllable OIDC endpoint to test client behavior in CI/local dev.","avoid_when":"You require strict compliance guarantees, production-grade security controls, or high-availability deployment characteristics.","alternatives":["Keycloak (dev/test realm)","Okta/Entra ID OIDC in sandbox mode","Auth0 test tenant","AppAuth/OIDC test toolchains and local brokers"],"af_score":30.2,"security_score":40.2,"reliability_score":27.5,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T21:32:56.195170+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":false,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["OIDC/OAuth2 endpoints typical for a mock provider (e.g., authorization, token, discovery, jwks)"],"oauth":false,"scopes":false,"notes":"Authentication method for callers is the OIDC flow itself; no evidence was provided here of API-key/OAuth scope design for administrative APIs."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No pricing information provided; treat as self-hosted tooling."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":30.2,"security_score":40.2,"reliability_score":27.5,"mcp_server_quality":0.0,"documentation_accuracy":30.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":60.0,"rate_limit_clarity":0.0,"tls_enforcement":60.0,"auth_strength":25.0,"scope_granularity":20.0,"dependency_hygiene":40.0,"secret_handling":60.0,"security_notes":"As a mock identity provider, it is likely not designed for production security guarantees. Ensure it is confined to test networks; do not reuse its keys/tokens in real environments. TLS enforcement cannot be confirmed from provided info, but typical deployments should use HTTPS.","uptime_documented":0.0,"version_stability":40.0,"breaking_changes_history":40.0,"error_recovery":30.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["OIDC flows often involve redirects and state/nonce handling; agents must persist cookies/query params across steps.","Mock providers may return non-production error shapes; clients may need tolerant parsing during testing.","JWKS/JWT signing keys and issuer/audience values must match client configuration exactly."]}}