[coverage] Conformance findings: AUTH-017

Abierto
  • ¿Algo no está bien?
#1,763 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
java
Área
authentication, backend

Línea de trabajo

Start with the coverage PR diff for testSessionOpenRequestsOneOAuthTokenAndFailsFastOnTokenFailure under tests/, then trace the OAuth token prefetch and session-open flow for the SEA path in this JDBC driver. Reproduce with the specified OAuth endpoint responses and verify the token-failure and token-success assertions, including token and connector-flag request counts and the expected CreateSession calls.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Summary

Surfaced by the multi-language coverage fan-out while conformance-testing these SPEC-IDs against databricks/databricks-jdbc. Each finding is committed as an expected-failure (xfail) test in the coverage PR — the test asserts the CORRECT (post-fix) behavior and stays red until THIS driver (databricks/databricks-jdbc) is fixed, then flips green as a tripwire.

Findings

  • AUTH-017 [sea]: On the SEA path a failed open-time OAuth token request (terminal 401 invalid_client) is swallowed and session-create immediately issues a SECOND token request with no backoff and ignoring Retry-After; the Thrift path correctly sends one (RE-17407)
    • failing test: testSessionOpenRequestsOneOAuthTokenAndFailsFastOnTokenFailure (see the coverage PR diff under tests/)

Reproduce & Expected

AUTH-017 — With OAuth M2M (client-credentials) auth AND a driver identity set — so the open-time connector-service feature-flag prefetch runs and is the first consumer of the auth provider — opening a session m…

Reproduce:

  • Point the OAuth token endpoint at an endpoint that answers every POST with
    HTTP 503 + Retry-After: 60, then attempt one cold open. Count the requests
    that endpoint received.
  • Cold open with a working token endpoint; observe the token, flag, and session requests.

Expected (per the shared spec):

  • completes without an exception
  • [thrift] exactly 0 OpenSession call(s)
  • [thrift] exactly 1 OpenSession call(s)
  • [sea] exactly 0 CreateSession call(s)
  • [sea] exactly 1 CreateSession call(s)
  • full assertion contract:
result:
- label: token_failure
  error:
    contains:
    - '503'
    - service unavailable
    - token
    - oauth
  description: 'The open fails with the TOKEN request''s error (the 503 / token failure),

    not a generic session-create failure and not a silent success.

    '
- label: token_failure
  connection_not_established: true
- label: token_failure
  oauth_token_fetch_count: 1
  description: 'The regression guard: before the fix the prefetch swallowed its token
    failure

    and cached nothing, so session-create immediately sent a SECOND token request

    with no backoff and ignoring `Retry-After`. Exactly one request must be sent.

    '
- label: token_failure
  connector_flag_fetch_count: 0
  description: 'Outcome check outside the core vocabulary (connector-service flag
    GETs seen at

    the proxy): the open aborts at authentication, so the prefetch never runs.

    '
- label: token_success
  no_exception: true
- label: token_success
  oauth_token_fetch_count: 1
  description: "One token serves BOTH the flag prefetch and the session-open request\
    \ \u2014 a\nsuccessful open costs exactly one token request.\n"
- label: token_success
  connector_flag_fetch_count: 1
protocol:
  thrift:
  - label: token_failure
    call_count:
      method: OpenSession
      expected: 0
  - label: token_success
    call_count:
      method: OpenSession
      expected: 1
  - label: token_success
    request_header:
      method: OpenSession
      name: Authorization
      present: true
  sea:
  - label: token_failure
    call_count:
      operation: CreateSession
      expected: 0
  - label: token_success
    call_count:
      operation: CreateSession
      expected: 1
  - label: token_success
    request_header:
      operation: CreateSession
      name: Authorization
      present: true

Context

Lenguaje dominante
Java
Estrellas
41
Forks
49
Merge medio
1 d 7 h
PR fusionados (30 d)
27

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de databricks/databricks-jdbc

Todos los issues de databricks/databricks-jdbc

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.