DNAnexus · OAuth Scopes

DNAnexus OAuth Scopes

OAuth 2.0 probed

DNAnexus publishes 4 OAuth 2.0 scopes via the authorizationCode flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the DNAnexus API on a user’s behalf.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

CompanyGenomicsBioinformaticsLife SciencesHealthcareCloud ComputingData PlatformScientific ComputingPrecision MedicineClinical Research

Scopes: 4 Flows: authorizationCode Method: probed

OAuth endpoints

Authorization URL
https://oidc.dnanexus.com/authorize

Flows
authorizationCode

Scopes (4)

Scope	Description	Flows
openid	Required OpenID Connect scope; requests an ID token for the signed-in DNAnexus user.	authorizationCode
name	Releases the DNAnexus user's display name as the `name` claim.	authorizationCode
email	Releases the DNAnexus user's email address as the `email` claim.	authorizationCode
user_id	Releases the DNAnexus platform user handle (user-xxxx) as the `user_id` claim.	authorizationCode

📄 Provider scope reference: https://documentation.dnanexus.com/developer/api/oidc-clients

Source

OAuth Scopes

generated: '2026-08-04'
method: probed
source: https://oidc.dnanexus.com/.well-known/openid-configuration
docs: https://documentation.dnanexus.com/developer/api/oidc-clients
note: >-
  The DNAnexus Platform API itself (api.dnanexus.com) is bearer-token authenticated
  and has NO OAuth scope surface - a token carries the full permissions of the user
  or job it was issued for, and access is instead constrained by project/org
  permission levels (VIEW / UPLOAD / CONTRIBUTE / ADMINISTER). The scopes below
  belong to the DNAnexus OpenID Connect provider, which third-party web apps use to
  sign users in.
schemes:
- name: DNAnexusOIDC
  issuer: https://oidc.dnanexus.com
  source: https://oidc.dnanexus.com/.well-known/openid-configuration
  flows:
  - flow: authorizationCode
    authorizationUrl: https://oidc.dnanexus.com/authorize
    pkce: S256
    response_types: [code]
scopes:
- scope: openid
  description: Required OpenID Connect scope; requests an ID token for the signed-in
    DNAnexus user.
  flows: [authorizationCode]
  claims: [sub, sid, auth_time, iss]
  sources: [https://oidc.dnanexus.com/.well-known/openid-configuration]
- scope: name
  description: Releases the DNAnexus user's display name as the `name` claim.
  flows: [authorizationCode]
  claims: [name]
  sources: [https://oidc.dnanexus.com/.well-known/openid-configuration]
- scope: email
  description: Releases the DNAnexus user's email address as the `email` claim.
  flows: [authorizationCode]
  claims: [email]
  sources: [https://oidc.dnanexus.com/.well-known/openid-configuration]
- scope: user_id
  description: Releases the DNAnexus platform user handle (user-xxxx) as the `user_id`
    claim.
  flows: [authorizationCode]
  claims: [user_id]
  sources: [https://oidc.dnanexus.com/.well-known/openid-configuration]
job_identity_provider:
  issuer: https://job-oidc.dnanexus.com
  source: https://job-oidc.dnanexus.com/.well-known/openid-configuration
  scopes: [openid]
  note: >-
    Job identity tokens support only the `openid` scope; the audience is set by the
    caller and the claim set (job_id, project_id, app_name, bill_to, region, ...)
    is what a relying cloud provider writes its trust policy against.
platform_permission_model:
  docs: https://documentation.dnanexus.com/developer/api/data-containers/project-permissions-and-sharing
  levels: [VIEW, UPLOAD, CONTRIBUTE, ADMINISTER]
  note: >-
    Project permission levels, not OAuth scopes, are the authorization surface for
    the Platform API.
x-evidence:
  fetched: '2026-08-04'
  http_status: 200