Skip to content

OpenID Connect 1.0 Configuration

TL;DR;

Integration Parameters

Discovery Document

In order to configure BadIdP as an OpenID Connect 1.0 identity provider, you must point your service provider to the OpenID Discovery configuration found at https://api.badidp.com/oidc/.well-known/openid-configuration (or otherwise configure it manually with the endpoint definitions there).

Credentials

No credentials are needed for BadIdP but if you need to provide a client_id and client_secret to your service provider, you may provide any values. BadIdP will accept/ignore all values.

OAuth2.0 Flow Support

BadIdP supports ALL valid and invalid OAuth2.0 flows and will respond adequately to any request from the service provider (i.e. handles all combinations of response_type and response_mode).

response_typeresponse_modeCommon Flow Name / AliasValid OAuth2.0BadIdP Support
codequery (default)Authorization Code Flow
codeform_postCode Flow with form POST
codefragmentCode Flow (nonstandard)
tokenfragment (default)Implicit Flow (Access Token only)
tokenqueryINVALID
tokenform_postINVALID
id_tokenfragment (default)OIDC Implicit Flow (ID Token only)
id_tokenform_postID Token via form POST
id_tokenqueryINVALID
id_token tokenfragment (default)OIDC Implicit Flow (ID Token + Access Token)
id_token tokenqueryINVALID
id_token tokenform_postINVALID
code id_tokenfragment (default)Hybrid Flow (Code + ID Token)
code id_tokenform_postHybrid Flow (secure POST)
code id_tokenqueryHybrid Flow (less common)
code tokenfragment (default)Hybrid Flow (Code + Access Token)
code tokenform_postHybrid Flow (form_post)
code tokenqueryHybrid Flow
code id_token tokenfragment (default)Hybrid Flow (All three)
code id_token tokenform_postFull Hybrid via form
code id_token tokenqueryHybrid Flow