gatesn opened a new issue, #584:
URL: https://github.com/apache/arrow-adbc/issues/584

   The docs suggest that the `authorization` header returned from the initial 
FlightSQL request will be sent on subsequent requests. I've tested that this 
does indeed happen for basic auth (username + password), but it doesn't happen 
when passing an initial authorization header.
   
   > The client provides credentials sending an authorization from client to 
server. The server then responds with an authorization header on the first 
request. The value of this header will then be sent back as the authorization 
header on all future requests.
   
   https://arrow.apache.org/adbc/0.3.0/driver/go/flight_sql.html#authentication
   
   e.g. with the following client code, and a FlightSQL server that changes the 
auth header to `Bearer bar` in its `AuthResult`, I would expect `Bearer bar` to 
be passed on all subsequent requests.
    
   ```python
   from adbc_driver_flightsql import dbapi, DatabaseOptions
   
   return dbapi.connect('grpc://localhost:8080', {
       DatabaseOptions.AUTHORIZATION_HEADER.value: 'Bearer foo' 
   })
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to