GP @CoderInCrisis @MorlockP and GorT: New payroll company has locked me out of its interface. They'd previously crossed my account with Tablet's account because same first initial, last name. Now I find they've set me up with TWO usernames. Does this strike you as not secure?
-
Show this thread
-
Replying to @Gormogons @MorlockP
Not so much a security problem as an administrative headache. Also entirely predictable. New system implementations are always painful.
2 replies 1 retweet 3 likes -
Replying to @CoderInCrisis @MorlockP
GP They're not assigning usernames. They're allowing users to choose usernames. Am I foolish for believing usernames should be assigned by the payroll company? Would've eliminated the problem and they had all employee data before migration.
1 reply 0 retweets 0 likes -
-
Replying to @CoderInCrisis @MorlockP
GP Hey, but I'm just a dipstick in the legal department.
3 replies 0 retweets 1 like -
GorT: I’m ok with user-chosen usernames (as long as they check & prevent duplicates). But sure, maybe issuing a standard username based on name, employee id, or something would help.
2 replies 0 retweets 0 likes -
Replying to @Gormogons @MorlockP
Yeah, there's nothing inherently wrong with letting users chose their own names, other than giving users a false sense of privilege.

Assigning usernames, especially if there's a lot of users, is just easier.2 replies 0 retweets 4 likes -
Replying to @CoderInCrisis @MorlockP
GP "username: 69xxx360noscopedotcomxxx69 password: urmomisahoor
1 reply 0 retweets 0 likes -
Replying to @Gormogons @MorlockP
Username: Pooter Password: T1ny!r1shW4ng I swear that password was totally random!
1 reply 0 retweets 4 likes -
Replying to @CoderInCrisis @MorlockP
GorT: please. username: Puter password: password (Error, must have an uppercase letter) password: pASSword (error, must have a number) password: pASSword1 (error, must have a symbol) password: pASSword1! (error, must be at least 14 characters long) GP: Dammit!
2 replies 0 retweets 0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.