4 replies
by dr dij
if what they can do with that login is very limited. for example on our plant floor, we leave a few PCs logged into time tracking app, and the assemblers / machine operators scan their employee badge and the barcode for the job step they're spending time on.
if said login can do anything that needs to be traceable, e.g. who rec'd these goods, that you now find are missing/damaged/miscounted, etc you need to have personal accountability.
including browsing the internet. we log sites and track them back to workstations to prevent users from wasting time and browsing to sites unrelated to work and potentially dangerous e.g. viruses from porn sites, etc.
There are only two ways to maintain a departmental password.
You never change it, or you have to find some way of communicating the change round the entire department.
Back in the bad old days I worked on system who did point 2. They used to write it on a bit of paper and stick it next to the terminal.
The third and potentially much more critical point from my point of view in terms of data collection, your system will have no idea who did what. So now you've no security and no audit trail, why bother with a password at all?
When we introduced single sign on's everybody said the job would stop, it didn't.
by rkuhn040172
We have a similar situation with our 20+ remote sites.
Most only have 128k ISDN (construction sites...that's usually all that is available).
Therefore, they aren't on our domain...not realistic with that kind of connection.
They logon locally with one sign on. After that though, all other software requires individual sign ons such as Citrix, ERP software, sales website, etc.
Sort of a hybrid model.
This discussion is closed to new replies.
Trending IT Employment posts
Sort by Trending