VSCode SAS Extension: Viya 4 2022.11 Endpoint Timeout

[Steve0verton]

I'm getting a timeout error when trying to start a session in VSCode.  The target environment is Viya 4 2022.11.  What does the network topology look like behind the scenes so I can make sure the security/firewall configuration is not blocking me??  I am getting the web page popup which gives me the authorization approval screen, which does give me the authorization code.  It fails after entering the code into VSCode with the timeout error.

[HarrySnart · Accepted solution]

Hi @Steve0verton did you have the extension working previously? When the extension was first released you had to add client id and secret to the config file to make a connection. I found that when the new version of the extension was released the connection failed because I had the client id and secret still in the config file. When I removed them and used the browser pop-up to login the issue was resolved. 

The profile in your settings.json file should look a bit like the below:

    "SAS.connectionProfiles": {

        "activeProfile": "<profile name>",

        "profiles": {

            "<profile>": {

                "endpoint": "<viya host>",

                "context": "SAS Job Execution compute context",

                "username": "<user>"

            }

        }

    }

[Steve0verton]

Yes this worked!  And I was coming from a previous version of Viya.

Also note, for those like me who keep k8s pods in an autoscaling mode to allow services to go to 0 and power down off hours.  You will have to wait approximately 5min before being able to connect to compute sessions within VSCode.  The first session of the day will fire up a compute pod.  I'm not sure how long the pod persists.  But if you have the symptom of a 60 second timeout, this could be it.  Monitor within Lens or kubectl to see when the compute service is fully running.