Joor · Authentication Profile

Joor Authentication

Authentication

Joor secures its APIs with openIdConnect and oauth2 across 1 declared security scheme, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode, clientCredentials, password, deviceCode, ciba, and implicit flow(s).

CompanyFashionWholesaleRetailE-CommerceB2BMarketplacePayments

Methods: openIdConnect, oauth2 Schemes: 1 OAuth flows: authorizationCode, clientCredentials, password, deviceCode, ciba, implicit API key in:

Security Schemes

openIdConnect openIdConnect

Source

Authentication Profile

generated: '2026-07-19'
method: searched
source: https://auth.jooraccess.com/auth/realms/joor/.well-known/openid-configuration
docs: https://auth.jooraccess.com/auth/realms/joor/.well-known/openid-configuration
summary:
  types: [openIdConnect, oauth2]
  oauth2_flows: [authorizationCode, clientCredentials, password, deviceCode, ciba, implicit]
  pkce: [S256, plain]
  provider: Keycloak
  gateway: Kong
schemes:
- name: openIdConnect
  type: openIdConnect
  openIdConnectUrl: https://auth.jooraccess.com/auth/realms/joor/.well-known/openid-configuration
  issuer: https://auth.jooraccess.com/auth/realms/joor
  endpoints:
    authorization: https://auth.jooraccess.com/auth/realms/joor/protocol/openid-connect/auth
    token: https://auth.jooraccess.com/auth/realms/joor/protocol/openid-connect/token
    userinfo: https://auth.jooraccess.com/auth/realms/joor/protocol/openid-connect/userinfo
    introspection: https://auth.jooraccess.com/auth/realms/joor/protocol/openid-connect/token/introspect
    end_session: https://auth.jooraccess.com/auth/realms/joor/protocol/openid-connect/logout
  grant_types:
  - authorization_code
  - client_credentials
  - refresh_token
  - password
  - implicit
  - urn:ietf:params:oauth:grant-type:device_code
  - urn:openid:params:grant-type:ciba
  token_endpoint_auth_methods:
  - private_key_jwt
  - client_secret_basic
  - client_secret_post
  - tls_client_auth
  - client_secret_jwt
  code_challenge_methods: [S256, plain]
  id_token_signing_alg_values: [RS256, ES256, PS256, RS384, ES384, PS384, RS512, ES512, PS512, HS256, HS384, HS512]
  sources: [well-known/joor-openid-configuration.json]
notes: >-
  Auth is derived from the live Keycloak OIDC discovery document (searched), not
  from a JOOR-published OpenAPI (none is public). client_credentials and
  private_key_jwt/tls_client_auth support indicate machine-to-machine and
  mTLS-capable integration clients; PKCE S256 is supported for public clients.

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this

find_securityBrowse and filter every security artifact in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This security artifact

curl "https://apis.io/api/v1/security/joor-authentication"

All security posture

curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.