Closed rmca-hl closed 9 months ago
Hi @rmca-hl , could you re-test the issue with newer versions? We made some updates lately both to vRDT and to Build Tools for Aria and it should be working now. Here is a sample result I got from one of my test actions:
I am running with the following config:
Feel free to re-open this issue if you find it still doesn't work on your side
Description
I am trying to leverage the explorer view in the vRDT VSCode extension while using 'vra' typed authentication, however, I am unable to load any assets. The explorer view works when using 'Basic' authentication and the same credentials.
Checking the Output logs in the vRealize Developer Tools view shows the following error:
Command 'mvn vrealize:auth -Pvro-poc -DoutputDir="C:\Users\dev_user\.o11n\tokens" -N -e' exited with code 1
I am able to run this manually in the console without issue. The returned JSON does not have an expirationDate field which I believe conflicts with the readTokenFile method in MavenCliProxy.
I tried adding my own expirationDate field to the JSON in an attempt to override this issue, but I'm still having a problem.
Steps to Reproduce
Expected behavior: Workflows/actions/etc. load when viewing the explorer in VSCode, as it does with basic auth.
Actual behavior: Nothing loads.
Reproduces how often: 100%
Environment
Client
Server
Failure Logs
[2022-07-11T22:13:19.596Z INFO - ShowWorkflows] Executing command Show Workflows [2022-07-11T22:13:25.288Z ERROR - VroRestClient] Command 'mvn vrealize:auth -Pvro-poc -DoutputDir="C:\Users\Dev User\.o11n\tokens" -N -e' exited with code 1 [2022-07-12T13:38:03.533Z ERROR - VroRestClient] Command 'mvn vrealize:auth -Pvro-poc -DoutputDir="C:\Users\Dev User\.o11n\tokens" -N -e' exited with code 1
Additional Context
There's been similar questions around this on the public slack channel.