Essendant Authentication

generated: '2026-09-07'
method: probed
source: https://sso.essendant.com/adfs/.well-known/openid-configuration
scope_note: >-
  Essendant publishes no public API and therefore no API authentication reference. What it
  DOES publish, anonymously and in machine-readable form, is OpenID Connect discovery
  metadata for the Active Directory Federation Services deployment that fronts its
  reseller and customer portals (Solutions Central, Azerty, BiggestBook, Empower Central).
  This file records that identity surface exactly as fetched. It is portal SSO, not an API
  authorization server: there is no dynamic client registration, no published client
  onboarding, and no resource server documented against it. Do not read this artifact as
  evidence of a developer program.
summary:
  types: [openIdConnect, oauth2]
  api_key_in: []
  oauth2_flows: [authorizationCode, clientCredentials, implicit, password, deviceCode, jwtBearer, refreshToken]
  mutual_tls: false
  dynamic_client_registration: false
  protected_resource_metadata: false
schemes:
- name: essendant-adfs-sso
  type: openIdConnect
  openIdConnectUrl: https://sso.essendant.com/adfs/.well-known/openid-configuration
  issuer: https://sso.essendant.com/adfs
  authorization_endpoint: https://sso.essendant.com/adfs/oauth2/authorize/
  token_endpoint: https://sso.essendant.com/adfs/oauth2/token/
  userinfo_endpoint: https://sso.essendant.com/adfs/userinfo
  device_authorization_endpoint: https://sso.essendant.com/adfs/oauth2/devicecode
  end_session_endpoint: https://sso.essendant.com/adfs/oauth2/logout
  jwks_uri: https://sso.essendant.com/adfs/discovery/keys
  token_endpoint_auth_methods_supported: [client_secret_post, client_secret_basic, private_key_jwt, windows_client_authentication]
  response_types_supported: [code, id_token, code id_token, id_token token, code token, code id_token token]
  grant_types_supported: [authorization_code, refresh_token, client_credentials, 'urn:ietf:params:oauth:grant-type:jwt-bearer', implicit, password, srv_challenge, 'urn:ietf:params:oauth:grant-type:device_code', device_code]
  id_token_signing_alg_values_supported: [RS256]
  subject_types_supported: [pairwise]
  frontchannel_logout_supported: true
  sources: [well-known/essendant-sso-openid-configuration.json]
- name: essendant-adfs-login
  type: openIdConnect
  openIdConnectUrl: https://login.essendant.com/adfs/.well-known/openid-configuration
  issuer: https://login.essendant.com/adfs
  authorization_endpoint: https://login.essendant.com/adfs/oauth2/authorize/
  token_endpoint: https://login.essendant.com/adfs/oauth2/token/
  userinfo_endpoint: https://login.essendant.com/adfs/userinfo
  device_authorization_endpoint: https://login.essendant.com/adfs/oauth2/devicecode
  end_session_endpoint: https://login.essendant.com/adfs/oauth2/logout
  jwks_uri: https://login.essendant.com/adfs/discovery/keys
  token_endpoint_auth_methods_supported: [client_secret_post, client_secret_basic, private_key_jwt, windows_client_authentication]
  grant_types_supported: [authorization_code, refresh_token, client_credentials, 'urn:ietf:params:oauth:grant-type:jwt-bearer', implicit, password, srv_challenge, 'urn:ietf:params:oauth:grant-type:device_code', device_code]
  id_token_signing_alg_values_supported: [RS256]
  sources: [well-known/essendant-login-openid-configuration.json]
federation:
- protocol: WS-Trust / WS-Federation
  metadata: https://sso.essendant.com/adfs/services/trust/mex
  http_status: 200
  format: WSDL 1.1 (WS-MetadataExchange)
  bytes: 26665
  note: >-
    Fetched and confirmed to parse as WSDL, but it is Microsoft's stock AD FS Security
    Token Service contract — targetNamespace
    http://schemas.microsoft.com/ws/2008/06/identity/securitytokenservice — not an API
    Essendant authored. Recorded as identity evidence only. Deliberately NOT registered as
    a WSDL contract in apis.yml: crediting a vendor-default STS endpoint as a published
    SOAP API would be a false positive on contract_present.
- protocol: SAML 2.0
  metadata: https://sso.essendant.com/FederationMetadata/2007-06/FederationMetadata.xml
  http_status: 200
  entity_id: http://sso.essendant.com/adfs/services/trust
  bytes: 82481
- protocol: SAML 2.0
  metadata: https://login.essendant.com/FederationMetadata/2007-06/FederationMetadata.xml
  http_status: 200
  entity_id: http://login.essendant.com/adfs/services/trust
  bytes: 81680
docs: null
docs_note: >-
  No public authentication documentation was found. Access to Essendant's portals and to
  the ECDB product-content feed is arranged through an account manager; Essendant directs
  integrators to TechSupport@Essendant.com rather than to a developer reference.