Added support for SigV4 authentication#2088
Conversation
Benefits: 1. Pluggable authentication - Authenticator trait allows OAuth2, SigV4, or custom auth 2. Backward compatible - Existing OAuth2 behavior preserved 3. Performance optimized - Signing key caching (valid for 24h) 4. Works with catalog implementations which use SigV4 Catalog implementation like MinIO use SigV4 authentication and it would be helpful for such cases. Signed-off-by: Shubhendu Ram Tripathi <shubhendu@minio.io>
|
Need some love from community for this change <3 |
|
This pull request has been marked as stale due to 30 days of inactivity. It will be closed in 1 week if no further activity occurs. If you think that’s incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the PR at any time and @mention a reviewer or discuss it on the dev@iceberg.apache.org list. Thank you for your contributions. |
|
We need some reviews on this. |
|
This pull request has been marked as stale due to 30 days of inactivity. It will be closed in 1 week if no further activity occurs. If you think that’s incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the PR at any time and @mention a reviewer or discuss it on the dev@iceberg.apache.org list. Thank you for your contributions. |
|
This pull request has been closed due to lack of activity. This is not a judgement on the merit of the PR in any way. It is just a way of keeping the PR queue manageable. If you think that is incorrect, or the pull request requires review, you can revive the PR at any time. |
1 participant
Which issue does this PR close?
Benefits:
Catalog implementation like MinIO use SigV4 authentication and it would be helpful for such cases.
What changes are included in this PR?
Adds support for SigV4 authentication
Are these changes tested?