ADH-8304: Do not apply WebUI auth filter to S3 API object paths#11
Merged
Conversation
S3 Gateway serves S3 object keys through the main webapp. When WebUI authentication is enabled, HttpServer2 maps initializer filters to *.html and *.jsp by default. This makes object keys such as page.html hit the WebUI/SPNEGO authentication filter before S3 SigV4 handling, causing PUT Object to fail with 401.
Asmoday
approved these changes
May 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR fixes S3G uploads for object keys ending with
.html/.jspwhen WebUI authentication is enabled.HttpServer2mapsAuthenticationFilterInitializerfilters to*.htmland*.jspon the main webapp by default. Since S3G serves S3 object API requests from the same main webapp, object paths like/bucket/page.htmlwere intercepted by the WebUI/SPNEGO filter before S3 SigV4 handling and failed with401 Unauthorized.The fix adds an internal
HttpServer2/BaseHttpServerhook to override main webapp filter path specs, and disables those WebUI filter mappings only for the S3 API server. S3G WebAdmin keeps the existing WebUI auth behavior.Changes
HttpServer2.Builder#setWebAppFilterPathSpecs.BaseHttpServer#getWebAppFilterPathSpecs.S3GatewayHttpServer.