workspaces-issues VS workspaces-stigs

See: https://github.com/kasmtech/workspaces-issues/issues/244

I just made a github bug report over at https://github.com/kasmtech/workspaces-issues/issues/368, but I'm curious to put out feelers and see if anyone else has noticed strange behavior from recent Kasm releases regarding this. Basically, when setting up a new Workspace based on a Windows RDP Server, the username/password field that used to automatically log in the session don't seem to do anything useful anymore. The dark horse possibility is this has something to do with my reverse proxy through Traefik, but my gut says this is unrelated- especially because it behaves the same when logging in and using Kasm locally. Logging in manually still works.

If you'd like to report the details about your upgrade problems , we'd be happy to take a look. You can file it here: https://github.com/kasmtech/workspaces-issues/issues

Hi, this is covered here: https://github.com/kasmtech/workspaces-issues/issues/350

General feedback can be given in this thread. For bugs or detailed troubleshooting it will be easier if you file an issue here: https://github.com/kasmtech/workspaces-issues/issues

Dont forget to leverage the docs, and issue tracker (https://github.com/kasmtech/workspaces-issues)

You may consider mentioning the details of your scenario on a similar open ticket: https://github.com/kasmtech/workspaces-issues/issues/47

We publish example ansible playbooks , terraform projects , and STIG hardening scripts. While not suitable for all deployment, hopefully it at least shows a bit about the posture of the organization.