[release/6.0-rc2] Fix krb5 library SO name in the gss api shim #59566
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.
Backport of #59526 to release/6.0-rc2
The library name used in the shim is a name of the build time library which
is usually installed only for development purposes. We should use
libgssapi_krb5.so.2 which is the underlying runtime library.
Close #59518
/cc @karelz @janvorli
Customer Impact
Kerberos authentication does not work in .NET 6.0 Docker images.
It is a regression again .NET 5.0 - introduced in single-file related changes (PR #55037).
Testing
CI runs. Local verification that the libgssapi_krb5.so.2 exists on Alpine, Ubuntu, Debian, FreeBSD and Redhat based distros.
Risk
Low. Wherever the originally used
libgssapi_krb5.so
is installed, the newly usedlibgssapi_krb5.so.2
is installed too, as it is the actual runtime library and thelibgssapi_krb5.so
is just a symlink to it.