plusplusjiajia commented on PR #3120: URL: https://github.com/apache/iceberg-python/pull/3120#issuecomment-4102892794
> Ok so from what ive gathered > > SigV4 is AWS's request signing mechanism. We're addressing the scenario where both SigV4 and OAuth are required for REST catalog authentication. The REST catalog requires an OAuth token, and AWS requires the request to also be SigV4-signed. The request is first authenticated by the delegate auth session, which stamps the OAuth bearer token into the Authorization header. That header is then relocated to Original-Authorization before SigV4 signs the request — freeing up Authorization for the SigV4 signature while keeping the OAuth token present and covered by the HMAC. > > Are you running your own IRC on AWS? i think [glue IRC](https://docs.aws.amazon.com/glue/latest/dg/connect-glu-iceberg-rest.html) doesnt need the oauth part We're planning to set up our own REST catalog with SigV4 signing. We don't use OAuth — just SigV4 for request authentication. This PR ensures the Python client produces signatures compatible with the Java Iceberg SDK's SigV4 implementation on the server side. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
