We have a few computers that are used by different users throughout the week depending on events happening in the room. We utilize the spark client to allow updates to those users without interrupting events in the room. We were using a shared Windows login, with spark usernames specific to the computer, so that each desk would get the message intended for it no matter who was sitting there.
I would like to change the machines to domain logins, but continue using one spark login for that machine no matter who logs in. I believe I can just change the spark.properties file to do that.
My questions are:
Are there any possible drawbacks to this setup that I should take in to account?
Can I “lock in” the username and password fields so that they cannot be changed?
I’m not quite sure if I fully understand your use-case, but I can’t identify downsides of what you write.
There are settings in Spark named “HIDE_SAVE_PASSWORD_AND_AUTO_LOGIN” and “ccPswdAutologin” that may help you lock down the credentials, but I’ve never tried using those myself.