Visual Studio Code Editor on Mac : blank error message when trying to log in. about vscode-sas-extension

[chulgyu100]

I also have same problem. Is it support Viya3.5?

[2TomLi]

We are creating a fix to remove the error message. Will update the extension soon.

[scnwwu]

v0.0.4 fixed the blank error in some cases. Some common problems gathered in https://github.com/sassoftware/vscode-sas-extension/wiki/FAQ

[sasrunner]

I am using newest version (0.0.6) and it has the the similar issue when connecting Viya 4 (stable 2022.1.2). The error message is "{}".

[scnwwu]

@sasrunner would you restart VS Code and try again to see what's the first error message? Some following error messages may not make sense when the process is already in a bad state.

[sasrunner]

I did restart VS code and it does not work. To give out more useful information, is there any debug option I can use?

…

On Tue, Jul 19, 2022 at 9:44 PM Wei Wu ***@***.***> wrote: @sasrunner <https://github.com/sasrunner> would you restart VS Code and try again to see what's the first error message? Some following error messages may not make sense when the process is already in a bad state. — Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACUQQAKEXZBAJYBVG6CNUSTVU5KZNANCNFSM5WF77XCQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[scnwwu]

Click "Help > Toggle Developer Tools" and see any errors/warnings in the Console

[sasrunner]

Hi Wei, Thank you. I have restarted my laptop and can see the error message (see below). {"status":401,"statusText":"Request failed with status code 401","detail":"{\"error\":\"invalid_client\",\"error_description\":\"Unauthorized grant type\"}","error":true} Do you have any idea on this?

…

On Wed, Jul 20, 2022 at 11:15 PM Wei Wu ***@***.***> wrote: Click "Help > Toggle Developer Tools" and see any errors/warnings in the Console — Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACUQQAO5KJMIR5YLLQLQWB3VVC6FBANCNFSM5WF77XCQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[scnwwu]

Was your client ID registered with the password grant type?

[sasrunner]

Hi Wei, Below is what I have done and I can see a blank message again. Note that I am following "Register a Client Using the CLI" per spec at https://go.documentation.sas.com/doc/en/sasadmincdc/v_022/calauthmdl/n1iyx40th7exrqn1ej8t12gfhm88.htm 1. Get Consul token: export NS=sas-xxx; \ export CONSUL_TOKEN=`kubectl -n ${NS} get secret sas-consul-client \ -o go-template='{{(index .data "CONSUL_HTTP_TOKEN")}}' | base64 -d` 2. Register the client by running the OAuth CLI. The command can run successfully.  3. in Visual Studio Code, set as follows:  Below is the snippet in the Console of Developer Tools.  Any thoughts?

…

On Thu, Jul 21, 2022 at 9:58 PM Wei Wu ***@***.***> wrote: Was your client ID registered with the password grant type? — Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACUQQAMA2Z2TRPWLC4M3IB3VVH54BANCNFSM5WF77XCQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[jefurbee]

Hi Kevin,
None of the images you added appear in the comment. All I see is [image: image.png]

[sasrunner]

Hi Kevin, None of the images you added appear in the comment. All I see is [image: image.png]

Thank you. Updated.

[scnwwu]

@sasrunner are you able to connect with token file? If you can generate access token in CLI, you can put it in a token file hopefully can bypass the grant type error.

[sasrunner]

Hi Wei, I am referring to "Obtain an Access Token Using Password Credentials" at https://go.documentation.sas.com/doc/en/sasadmincdc/v_030/calauthmdl/n1iyx40th7exrqn1ej8t12gfhm88.htm#n1n9seeyh7rsg7n1iilbj8wxnyxo curl "${INGRESS_URL}/SASLogon/oauth/token" \ -H "Content-Type: application/x-www-form-urlencoded" \ -d "grant_type=password&username=sastest&password=xxxxx" \ -u "vsc3:vsc_viya3" With token file, I get new error message: { "service": "compute", "detail": { "status": 401, "statusText": "Request failed with status code 401", "detail": "{\"version\":2,\"httpStatusCode\":401,\"errorCode\":401,\"message\":\"Full authentication is required to access this resource\",\"details\":[\"path: /compute/\",\"correlator: 20fb1ece-d9e2-483c-92f3-43d39056b561\"]}", "error": true } } Any thoughts?

…

On Tue, Jul 26, 2022 at 10:36 PM Wei Wu ***@***.***> wrote: @sasrunner <https://github.com/sasrunner> are you able to connect with token file? If you can generate access token in CLI, you can put it in a token file hopefully can bypass the grant type error. — Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACUQQAL7FQVHSOOZHNYTW5DVWCOCXANCNFSM5WF77XCQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>