Skip to content

Improvements for NEGOTIATE usage - #7285

Merged
dagnir merged 2 commits into
feature/master/netty-kerberos-proxy-authfrom
dongie/netty-negotiate-javadoc
Aug 17, 2026
Merged

Improvements for NEGOTIATE usage#7285
dagnir merged 2 commits into
feature/master/netty-kerberos-proxy-authfrom
dongie/netty-negotiate-javadoc

Conversation

@dagnir

@dagnir dagnir commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

Motivation and Context

Modifications

Testing

Screenshots (if appropriate)

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)

Checklist

  • I have read the CONTRIBUTING document
  • Local run of mvn install succeeds
  • My code follows the code style of this project
  • My change requires a change to the Javadoc documentation
  • I have updated the Javadoc documentation accordingly
  • I have added tests to cover my changes
  • All new and existing tests passed
  • I have added a changelog entry. Adding a new entry must be accomplished by running the scripts/new-change script and following the instructions. Commit the new file created by the script in .changes/next-release with your changes.
  • My change is to implement 1.11 parity feature and I have updated LaunchChangelog

License

  • I confirm that this pull request can be released under the Apache 2 license

dagnir added 2 commits August 17, 2026 13:58
NEGOTIATE depends on ambient, expiring, host-level state rather than on
anything the customer passes to the builder, and none of that was
documented. Spell out on the enum constant that credentials come from
the ticket cache and never from a prompt or keytab, that a missing or
expired ticket is not detected at build time and instead fails when a
proxy connection is established, that the service principal is derived
from the configured proxy host so an IP literal will not work, and that
the JDK's GSS and JAAS modules must be present in the runtime image.

Also note on the builder setter that username and password are ignored
for NEGOTIATE, so credentials left in place while switching schemes are
not silently assumed to be in use.
NEGOTIATE authenticates from the Kerberos ticket cache, so a username
and password configured alongside it are dead configuration. Switching
an existing Basic proxy configuration over to NEGOTIATE and leaving the
credentials in place therefore looks like it still uses them, with no
signal either way.

Warn at build() rather than reject, and only when the credentials were
set directly on the builder: values resolved from system properties or
environment variables may not be under the caller's control, so warning
about those would be noise they cannot act on.
@dagnir
dagnir requested a review from a team as a code owner August 17, 2026 21:05
@dagnir
dagnir requested a review from Fred1155 August 17, 2026 21:08
@dagnir
dagnir merged commit 42be292 into feature/master/netty-kerberos-proxy-auth Aug 17, 2026
4 checks passed
@github-actions

Copy link
Copy Markdown

This pull request has been closed and the conversation has been locked. Comments on closed PRs are hard for our team to see. If you need more assistance, please open a new issue that references this one.

@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Aug 17, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants