generated: '2026-07-18' method: searched source: https://auth.circuithub.com/.well-known/openid-configuration notes: >- CircuitHub has no public developer API and therefore no OpenAPI security schemes to derive from. End-user authentication for the CircuitHub web application (app.circuithub.com) is handled by an Auth0-hosted OpenID Connect tenant at auth.circuithub.com. The profile below is read verbatim from that tenant's published OIDC discovery document. summary: types: [openIdConnect, oauth2] provider: Auth0 oauth2_flows: [authorizationCode, clientCredentials, deviceCode, implicit] pkce: true schemes: - name: OpenIDConnect type: openIdConnect provider: Auth0 issuer: https://auth.circuithub.com/ openIdConnectUrl: https://auth.circuithub.com/.well-known/openid-configuration authorization_endpoint: https://auth.circuithub.com/authorize token_endpoint: https://auth.circuithub.com/oauth/token userinfo_endpoint: https://auth.circuithub.com/userinfo jwks_uri: https://auth.circuithub.com/.well-known/jwks.json device_authorization_endpoint: https://auth.circuithub.com/oauth/device/code revocation_endpoint: https://auth.circuithub.com/oauth/revoke end_session_endpoint: https://auth.circuithub.com/oidc/logout code_challenge_methods_supported: [S256, plain] grant_types_supported: - authorization_code - client_credentials - refresh_token - implicit - urn:ietf:params:oauth:grant-type:device_code - urn:ietf:params:oauth:grant-type:token-exchange token_endpoint_auth_methods_supported: - client_secret_basic - client_secret_post - private_key_jwt - none id_token_signing_alg_values_supported: [RS256, PS256, HS256] dpop_signing_alg_values_supported: [ES256] scopes_supported: - openid - profile - offline_access - name - given_name - family_name - nickname - email - email_verified - picture - created_at - identities - phone - address sources: [well-known/circuithub-openid-configuration.json]