You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we're trying to connect to a 2022.09 LTS cluster through the nginx ingress using the latest SWAT package. The constructor call fails with this message:
This is similar to an issue we've found here, but note that our error actually lists a CAS session reference which looks ok. The log output seems to indicate that the 1st REST call returns a valid session reference which is not recognized by the 2nd call?
There are no related error messages in the CAS log. How can we further debug this? (on the SAS/Kubernetes side maybe?). The Viya environment is hosted on AWS.
I'm closing this one - it turned out that the problem was caused by a case mismatch in the user ID - we had to make sure to enter the user ID "all uppercase" ("MYUSERID" vs. "myuserid"). I also just found this setting: env.CASUSERIGNORECASE='ON' which should make things even easier.
Hi,
we're trying to connect to a 2022.09 LTS cluster through the nginx ingress using the latest SWAT package. The constructor call fails with this message:
SWATError: Unknown session.: 3dfeb19a-09e2-674e-ad1e-ab78338ff9af
This is similar to an issue we've found here, but note that our error actually lists a CAS session reference which looks ok. The log output seems to indicate that the 1st REST call returns a valid session reference which is not recognized by the 2nd call?
There are no related error messages in the CAS log. How can we further debug this? (on the SAS/Kubernetes side maybe?). The Viya environment is hosted on AWS.
Thanks for looking into this!
Here's our test code:
This is the log output (abbreviated):
The text was updated successfully, but these errors were encountered: