Vault 10 classic client generates invalid ULR for work items.

[ns88ns]

Hi, Support.

I found a problem with the Vault classic client 10.2.0(31222):

When I try to open any work item in browser via "View Item In Browser" - the client generates invalid URL like "https//scv.myserver.la...blah..." with no colon after "https".

E.g.: the valid URL of the work item is:
"https://myserver_fqdn/VaultPro/Item.aspx?pid=100&itemid=4087&mode=view"

but the Vault client generates:
"https//myserver_fqdn/VaultService/VaultPro/Item.aspx?pid=100&itemid=4087&mode=view"

I checked all articles on this forum but found nothing similar. I never used this feature before but today I tried and found this problem.

Could you assist me with isolation and resolution?

Thank you in advance.
Regards.

[Tonya]

Hello,

What browser and version do you have installed? Can you please try open the work item using a different browser to see if the issue is specific to a particular browser? I am unable to reproduce the problem.

Thanks,

Tonya

[ns88ns]

Hi, Tonya.
Thank you for reply.

I re-investigated the issue and found a stable repro-case. My default browser is Google Chrome, the latest release but the browser doesn't matter.

The problem is reproduced if the Vault Classic client is configured for auto-login. See below.

1. Check you're logged out from the Vault Web client;
2. Close your default browser;
3. Open the Vault classic client and configure it for auto-login to a defined repository (via "Automatically connect using this profile");
4. Close the Vault classic client;
5. Open the Vault classic client, it logs in automatically using the configured profile;
6. Navigate to Work Items and open any.
7. Now click "View Item in Browser" --> the problem is reproduced here;
8. Disconnect from the Vault server via File -> Disconnect from server;
9. Connect back to the same Vault server via File -> Connect to server;
10. Navigate to Work Items and open any.
11. Now click "View Item in Browser" --> the problem is not reproduced anymore;

This problem is not reproduced if the Vault Classic client is not configured for auto-login.

This problem is not reproduced in the Vault VS plugin because it always asks for creds/profile to log in to the Vault server, even if auto-login is configured.

Could you, please, check if the scenario above is reproducible in your environment?

Regards,

[Tonya]

Hello again,

Thank you for all the details. I am still unable to reproduce the problem. Would you mind to provide us with a screenshot of what appears when you attempt to "View item in browser"? Have you tried a different machine?

Tonya

[ns88ns]

Sure, please see:

In google Chrome:

_sgc_err_1.png

In Microsoft Edge:

_sgc_err_2.png

I checked the repro-case on several systems - and it is reproducible. I'm not sure, but (just a thought) can it be related to the system locale/language? All my systems where I see this issue are not on EN-US.

Regards,

[Tonya]

Hello again,

Thank you for the screenshots, they were helpful. So I was able to reproduce the issue today. I believe I needed to log out and log back in with the profile a second time, then I was able to get the error that you received. This is a bug that has already been logged (18326). It will be considered in a future release.

Thank you for taking the time to point on the issue to us.

Tonya

[ns88ns]

Hi, Tonya.

Got it. Thank you for investigation and clarification.

Regards.

[Tonya]

Vault 11 was just recently released so perhaps it will make a minor version.

Tonya