Niteshift · Authentication Profile

Niteshift Authentication

Authentication

Niteshift secures its APIs with oauth2 and openIdConnect across 2 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode, deviceCode, clientCredentials, and refreshToken flow(s).

CompanyInfrastructureCoding AgentsAI AgentsDeveloper ToolsCloud Development EnvironmentsDevOpsAutomation
Methods: oauth2, openIdConnect Schemes: 2 OAuth flows: authorizationCode, deviceCode, clientCredentials, refreshToken API key in:

Security Schemes

OAuth2 oauth2
OpenIDConnect openIdConnect

Source

Authentication Profile

niteshift-authentication.yml Raw ↑
generated: '2026-07-20'
method: searched
source: https://niteshift.dev/.well-known/oauth-authorization-server
docs: https://auth.niteshift.dev/.well-known/openid-configuration
summary:
  types: [oauth2, openIdConnect]
  oauth2_flows: [authorizationCode, deviceCode, clientCredentials, refreshToken]
  pkce: [S256]
  oidc: true
schemes:
  - name: OAuth2
    type: oauth2
    issuer: https://auth.niteshift.dev
    grant_types:
      - authorization_code
      - refresh_token
      - client_credentials
      - urn:ietf:params:oauth:grant-type:device_code
    authorization_endpoint: https://auth.niteshift.dev/oauth2/authorize
    token_endpoint: https://auth.niteshift.dev/oauth2/token
    device_authorization_endpoint: https://auth.niteshift.dev/oauth2/device_authorization
    introspection_endpoint: https://auth.niteshift.dev/oauth2/introspection
    registration_endpoint: https://auth.niteshift.dev/oauth2/register
    userinfo_endpoint: https://auth.niteshift.dev/oauth2/userinfo
    jwks_uri: https://auth.niteshift.dev/oauth2/jwks
    code_challenge_methods_supported: [S256]
    token_endpoint_auth_methods_supported: [none, client_secret_post, client_secret_basic]
    sources: [well-known/niteshift-oauth-authorization-server.json]
  - name: OpenIDConnect
    type: openIdConnect
    openIdConnectUrl: https://auth.niteshift.dev/.well-known/openid-configuration
    id_token_signing_alg_values_supported: [RS256]
    subject_types_supported: [public]
    sources: [well-known/niteshift-openid-configuration.json]
notes: >-
  Auth profile derived from Niteshift's published RFC 8414 authorization-server
  metadata and OIDC discovery document (no provider OpenAPI is published).
  Supports Dynamic Client Registration (RFC 7591) and the OAuth 2.0 Device
  Authorization Grant, consistent with a CLI / coding-agent client model.