Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need help with Container Credential Guard service resolution of gMSA tickets for Windows Containers #422

Closed
jterry75 opened this issue Sep 15, 2023 · 5 comments
Labels
gMSA authentication account across containers question Further information is requested triage New and needs attention

Comments

@jterry75
Copy link

We are attempting to use domainless gMSA based on the public documentation provided from Microsoft here: https://learn.microsoft.com/en-us/windows-server/security/group-managed-service-accounts/group-managed-service-accounts-overview and here: https://learn.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/manage-serviceaccounts and plugin API here: https://learn.microsoft.com/en-us/windows/win32/api/ccgplugins/nn-ccgplugins-iccgdomainauthcredentials.

Note that we have all of this working for our common scenarios. However, we have an additional scenario where the network namespace of the container's needs to be isolated from the host for various security policy reasons.

The architecture looks like this:

  1. Host has a Network Interface that is attached to an internal network.
  2. Host has a Network Interface that is attached to private subnet that has access to the domain controller.
  3. We create a Transparent network namespace and attach the Network Interface of the private subnet to it.
  4. We disable the Network Interface in the host compartment. This now fully isolates all container traffic from the host. The host cannot send traffic into the private subnet, and the container has no access to the host network.
  5. We then attempt to use domainless gMSA and find that the CCG service cannot resolve the domain.

It appears that CCG uses the DNS resolution of the primary network interface in the host compartment. This means that the primary network adapter of the instance must be on the same network as the domain controller. How can we configure CCG to resolve the kerberos ticket using the DNS of the container network instead of the primary nic?

Thanks!

@jterry75 jterry75 added the question Further information is requested label Sep 15, 2023
@ntrappe-msft ntrappe-msft added triage New and needs attention gMSA authentication account across containers labels Sep 19, 2023
@fady-azmy-msft
Copy link
Contributor

fady-azmy-msft commented Oct 18, 2023

I'm not sure what the right answer is to your question, but I've reached out to the team that owns CCG if they can comment here.

@vrapolinario
Copy link
Contributor

Hi @jterry75 long time... Have you tried to change the network priority instead on this host? I'm assuming the network interface you don't want to use has a higher priority and is not the right DNS resolution, but not sure...

@arun-annamalai
Copy link

We would like to keep the network priority of the primary network interface as the highest. Is there another way to configure CCG.exe so that the binary runs in the network interface in step 2?

Copy link
Contributor

This issue has been open for 30 days with no updates.
no assignees, please provide an update or close this issue.

@vrapolinario
Copy link
Contributor

At this time configuring the network adapter for CCG is not supported. CCG will use the host's network which must have line of sight to the DC.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
gMSA authentication account across containers question Further information is requested triage New and needs attention
Projects
None yet
Development

No branches or pull requests

5 participants