1. Describe the bug
Docker has release a new technology called Docker Sandboxes, which allows you to run coding agents in secure boundaries: https://docs.docker.com/ai/sandboxes/. Using the AL MCP from there works well in general. There is a nice feature though that is not really compatible: You can manage credentials on the host of the sandbox and have it inject that into network traffic coming out of the sandbox. The idea is that an agent, MCP or similar within the sandbox is never even seeing the credential, making it impossible to steal it: https://docs.docker.com/ai/sandboxes/security/credentials/.
That would mean that in such a setup, I would have a launch.json with UserPassword auth and use it from within the sandbox. In this case, the AL MCP tools should just assume that auth is handled somewhere else and make the call to the BC instance without asking the user for user / pwd. I would prefer that as an instruction to the AL MCP, not as part of the launch.json config as I might use the same config with and without the sandbox setup. But I could also have two configs within the launch.json, so something like neverAskForUserPwd as part of the launch.json config would also solve the issue
2. To Reproduce
Steps to reproduce the behavior are explained on https://tobiasfenster.io/docker-sandbox-credential-injection-for-business-central. Here I use "Windows" auth in the launch.json as workaround, but I would prefer to properly handle it with "UserPassword"
3. Expected behavior
I would like a way to configure that calling the relevant AL tools doesn't ask for user/pwd even if "UserPassword" auth is configured in launch.json
4. Actual behavior
Calling the AL tools with "UserPassword" auth in launch.json always causes a request for user/pwd
5. Versions:
I don't think that part is relevant for my issue, but let me know if you still want it
- AL Language:
- Visual Studio Code:
- Business Central:
- List of Visual Studio Code extensions that you have installed:
- Operating System:
Final Checklist
Please remember to do the following:
1. Describe the bug
Docker has release a new technology called Docker Sandboxes, which allows you to run coding agents in secure boundaries: https://docs.docker.com/ai/sandboxes/. Using the AL MCP from there works well in general. There is a nice feature though that is not really compatible: You can manage credentials on the host of the sandbox and have it inject that into network traffic coming out of the sandbox. The idea is that an agent, MCP or similar within the sandbox is never even seeing the credential, making it impossible to steal it: https://docs.docker.com/ai/sandboxes/security/credentials/.
That would mean that in such a setup, I would have a launch.json with UserPassword auth and use it from within the sandbox. In this case, the AL MCP tools should just assume that auth is handled somewhere else and make the call to the BC instance without asking the user for user / pwd. I would prefer that as an instruction to the AL MCP, not as part of the launch.json config as I might use the same config with and without the sandbox setup. But I could also have two configs within the launch.json, so something like
neverAskForUserPwdas part of the launch.json config would also solve the issue2. To Reproduce
Steps to reproduce the behavior are explained on https://tobiasfenster.io/docker-sandbox-credential-injection-for-business-central. Here I use "Windows" auth in the launch.json as workaround, but I would prefer to properly handle it with "UserPassword"
3. Expected behavior
I would like a way to configure that calling the relevant AL tools doesn't ask for user/pwd even if "UserPassword" auth is configured in launch.json
4. Actual behavior
Calling the AL tools with "UserPassword" auth in launch.json always causes a request for user/pwd
5. Versions:
I don't think that part is relevant for my issue, but let me know if you still want it
Final Checklist
Please remember to do the following:
Search the issue repository to ensure you are reporting a new issue
Reproduce the issue after disabling all extensions except the AL Language extension
Simplify your code around the issue to better isolate the problem