Lifetise Authentication

generated: '2026-07-26'
method: searched
source: https://auth.coadjute.com/.well-known/openid-configuration
docs: https://www.coadjute.com/coadjute-partner-terms-of-service
raw:
- well-known/lifetise-openid-configuration.json
- well-known/lifetise-oauth-authorization-server.json
- authentication/coadjute-openid-configuration.json
note: |
  Derived from the only anonymously fetchable machine-readable contract Coadjute
  publishes: the Auth0-backed OpenID Connect discovery document on auth.coadjute.com.
  There is no OpenAPI to derive securitySchemes from — api.coadjute.com is fully gated
  and developer.coadjute.com returns 502 — so this profile records the identity layer as
  advertised by the tenant plus the manually provisioned partner token path evidenced by
  a third-party CRM integration page. Nothing here is inferred beyond those two sources.
summary:
  types: [oauth2, openIdConnect, apiKey]
  api_key_in: [header]
  oauth2_flows: [authorizationCode, clientCredentials, deviceCode, password, implicit, tokenExchange, jwtBearer]
  pkce: true
  pkce_methods: [S256, plain]
  mfa: true
  dpop: true
  dynamic_client_registration: true
schemes:
- name: coadjute-oidc
  type: openIdConnect
  openIdConnectUrl: https://auth.coadjute.com/.well-known/openid-configuration
  issuer: https://auth.coadjute.com/
  provider: Auth0
  sources: [well-known/lifetise-openid-configuration.json]
  endpoints:
    authorization: https://auth.coadjute.com/authorize
    token: https://auth.coadjute.com/oauth/token
    userinfo: https://auth.coadjute.com/userinfo
    jwks: https://auth.coadjute.com/.well-known/jwks.json
    registration: https://auth.coadjute.com/oidc/register
    revocation: https://auth.coadjute.com/oauth/revoke
    device_authorization: https://auth.coadjute.com/oauth/device/code
    mfa_challenge: https://auth.coadjute.com/mfa/challenge
    backchannel_authentication: https://auth.coadjute.com/bc-authorize
    global_token_revocation: https://auth.coadjute.com/oauth/global-token-revocation/connection/{connectionName}
  id_token_signing_alg_values_supported: [HS256, RS256, PS256]
  token_endpoint_auth_methods_supported: [client_secret_basic, client_secret_post, private_key_jwt, none]
  token_endpoint_auth_signing_alg_values_supported: [RS256, RS384, PS256]
  response_types_supported: [code, token, id_token, code token, code id_token, token id_token, code token id_token]
  response_modes_supported: [query, fragment, form_post]
  subject_types_supported: [public]
  code_challenge_methods_supported: [S256, plain]
  dpop_signing_alg_values_supported: [ES256]
  backchannel_logout_supported: true
  backchannel_token_delivery_modes_supported: [poll]
  request_parameter_supported: false
  request_uri_parameter_supported: false
- name: coadjute-oauth2
  type: oauth2
  sources: [well-known/lifetise-oauth-authorization-server.json]
  grant_types_supported:
  - client_credentials
  - authorization_code
  - refresh_token
  - password
  - implicit
  - urn:ietf:params:oauth:grant-type:device_code
  - urn:ietf:params:oauth:grant-type:token-exchange
  - urn:ietf:params:oauth:grant-type:jwt-bearer
  - http://auth0.com/oauth/grant-type/password-realm
  - http://auth0.com/oauth/grant-type/passwordless/otp
  - http://auth0.com/oauth/grant-type/mfa-oob
  - http://auth0.com/oauth/grant-type/mfa-otp
  - http://auth0.com/oauth/grant-type/mfa-recovery-code
  authorization_grant_profiles_supported:
  - urn:ietf:params:oauth:grant-profile:id-jag
  scopes: scopes/lifetise-scopes.yml
- name: coadjute-partner-token
  type: apiKey
  in: header
  provisioning: manual
  self_serve: false
  sources:
  - https://www.street.co.uk/integrations/coadjute
  evidence: |
    Street's Coadjute integration page instructs agents to email street@coadjute.com for
    a guide on "how to enable webhooks and obtain your API token" — credentials for the
    Partner Cloud API are issued by a human under a signed partner agreement. The header
    name and token format are not published anywhere public.
    Corroborated by the NeosAlpha case study describing a Kong API gateway fronting
    Coadjute's partner APIs with an "OAuth2.0-based security model".
access:
  gate: partner-only
  self_serve_signup: false
  what_is_required: |
    A signed Coadjute Partner Terms of Service with an Order Form and Subscription Term.
    There is no developer signup: every public conversion path is "Book a demo",
    "Request access" or "Login".
claims_supported: [aud, auth_time, created_at, email, email_verified, exp, family_name,
  given_name, iat, identities, iss, name, nickname, phone_number, picture, sub]
probes:
- {url: 'https://auth.coadjute.com/.well-known/openid-configuration', status: 200}
- {url: 'https://auth.coadjute.com/.well-known/oauth-authorization-server', status: 200}
- {url: 'https://auth.coadjute.com/.well-known/jwks.json', status: 200, saved: false, note: rotating key material}
- {url: 'https://api.coadjute.com/.well-known/openid-configuration', status: 401}