You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I fixed the target hostname for the fake KDC inside the KDC proxy. I tried to write the minimal possible solution.
The problem: during the credentials injection, the RDP client does the Kerberos authentication via a KDC proxy with a fake KDC. In that case, the target hostname (Kerberos service name for the TGS) must be a proxy hostname. But prior to this PR, the KDC proxy always configured the internal KDC to the real target machine hostname. This problem was introduced in #1768.
For example, my local configuration:
Devolutions-Gateway hostname: dgateway.tbt.com.
Target machine behind the proxy: WIN-956CQOSSJTF.tbt.com.
When I connect to the target machine using credentials injection, my FreeRDP command looks like this:
Let maintainers know that an action is required on their side
Add the label
release-requiredPlease cut a new release (Devolutions Gateway, Devolutions Agent, Jetsocat, PowerShell module)
when you request a maintainer to cut a new release (Devolutions Gateway, Devolutions Agent, Jetsocat, PowerShell module)
Add the label
release-blockerFollow-up is required before cutting a new release
if a follow-up is required before cutting a new release
Add the label
publish-requiredPlease publish libraries (`Devolutions.Gateway.Utils`, OpenAPI clients, etc)
when you request a maintainer to publish libraries (Devolutions.Gateway.Utils, OpenAPI clients, etc.)
Add the label
publish-blockerFollow-up is required before publishing libraries
if a follow-up is required before publishing libraries
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
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.
Hi,
I fixed the target hostname for the fake KDC inside the KDC proxy. I tried to write the minimal possible solution.
The problem: during the credentials injection, the RDP client does the Kerberos authentication via a KDC proxy with a fake KDC. In that case, the target hostname (Kerberos service name for the TGS) must be a proxy hostname. But prior to this PR, the KDC proxy always configured the internal KDC to the real target machine hostname. This problem was introduced in #1768.
For example, my local configuration:
dgateway.tbt.com.WIN-956CQOSSJTF.tbt.com.When I connect to the target machine using credentials injection, my FreeRDP command looks like this:
During the FreeRDP's NLA stage, it should perform Kerberos auth against
dgateway.tbt.com(instead ofWIN-956CQOSSJTF.tbt.com).I hope I explained the problem well 😄.