?This is just a heads up to everyone.
I just got off of a 2 hour session with TB regarding secure user connections to the processor.
Here's the rundown:
- CP4 processor running the latest firmware
- TSW-1070 running the latest firmware
- TSR-310s running 2.001.0078.001 firmware
- Everything setup using SSL and all cloud junk turned off.
- User setup in the system for local Crestron devices as a "connects" user.
TSW-1070 connects perfectly using setcsauthentication.
TSR -310s can't connect at all and are added to the blocked user list.
CP4 logs the error regarding the remotes.
Added a new user just for the TSRs to connect to and increased the authorization level from connects to user.? Still no connections.
Upgraded the firmware of one TSR to the version released this morning.? Cleared everything out, rebooted, and added it all back in ... still no connection.
TB support told me that mobile device users for projects that are hosted on the processor are now required to be authorization level of operators.
So, he said why not try that "just for kicks", although this shouldn't be the case for "non-hosted" projects.
Added a new user for the TSRs with operator user level, cleared out the remotes and blocked users, rebooted everything, and added csauthentication and IP Table entries.
Woohoo!!!? TSR with the latest firmware (2.001.0095.001) connects!? TSR with the last version fails to connect.
This is all getting quite ridiculous!
TB couldn't explain why the TSW connected fine with a lower user level but the TSRs wouldn't.
Yet another mystery related to new firmware combinations!
So, when in doubt, set the authentication for device connections to an operator.
Good luck!
Brian
Ryan Cunningham