Closed tfenster closed 1 year ago
Additional note: If I use the BC 19 onprem artifacts, the connection works
New-BcContainer -accept_eula -accept_outdated -containerName onprem19fr -artifactUrl (Get-BCArtifactUrl -type onprem -country fr -version 19) -imageName mybc -auth NavUserPassword
[2021-11-04 17:21:25.23] Initializing a snapshot debugging request on debugging context :d3e5aa6d-4348-4768-bd49-db98b9b8b19b
[2021-11-04 17:21:25.23] Sending request to https://snap-test.germanywestcentral.cloudapp.azure.com/onprem19frsnap/snapshotdebugger/attach?debuggingcontext=d3e5aa6d-4348-4768-bd49-db98b9b8b19b
[2021-11-04 17:21:26.03] The snapshot debugger initialize request for the debugging context 'd3e5aa6d-4348-4768-bd49-db98b9b8b19b' has succeeded.
Check the status of an initialized snapshot by using the 'Show all snapshots' command, or by clicking the snapshot debugger icon in the left corner of the toolbar.
So it seems like this is somehow connected to the sandbox artifacts?
If you add -runSandboxAsOnPrem does that make it work?
Yes, that works. Shouldn't it also work without that?
Yes, it should - but it points to where the error is (in the permission subsystem)
@freddydk any idea on this yet?
hmmm, took me some time to figure out the configuration. This one was working for me.
{
"name": "snapshotInitialize: MyServer",
"type": "al",
"request": "snapshotInitialize",
"environmentType": "OnPrem",
"server": "https://yourserver.westeurope.cloudapp.azure.com",
"port": 443,
"serverInstance": "navserversnap",
"authentication": "UserPassword",
"breakOnNext": "WebClient"
},
@freddydk any update on this?
Hi, adding "tenant": "default"
to the Snapshot Debugger configuration in the launch.json
should solve the issue. This is because sandbox containers are multitenant by default, so this parameter is required when connecting to the container.
Describe the issue When trying to initialize a snapshot debugging session, I am asked for username and password, but they aren't accepted. The same username and password work for e.g. downloading symbols. Here is what I do:
Scripts used to create container and cause the issue
Full output of scripts
Screenshots
Additional context
I also checked the BC Server configuration, but Snapshot debugging seems enabled and on the right port
As I get an auth problem and not something like a 404, it also seems to me like it works in general