Username format?

hello people, quick question. I was wondering what was your favorite username format to use as a network administrator at a business. We are going through major transistions in our internal network and I am looking for a new way to identify users through the network and company. I really don't want to use first and last names because we are constantly having to change usernames due to name changes. I was thinking about this format:

Birthday 01/02/2005 SS#123-56-7890

username:027890



What do you think?

I wouldn't use anything like the SS number in something like this ...........
just me being paranoid ............ BUT.

couldn't you generate numbers based on their names / DOB / payroll # - WHEN THEY JOINED ?

what's wrong with having to change a few names once in a while ?
Just call EVERYONE [L]user, with password as the password.

problem solved :)

NEXT :p

what i am trying to do is create a universal I.D. that I could implement for this organization. I would like to create a ldap structure with smartcard access. I have different opinions for the last 4 characters of the SS number. I see no problem with that. We have multiple systems here at this facility that requires so many characters to a username. Usually at eight, but we have one system that uses six characters. So that is why I created the ID above. The chances are low for someone to have the same user id.

Here in Canada.......I would NEVER tell anyone...or for that matter ...let anyone USE my SIN..(SS in US terms)

You may be in privacy rights violation...

I group by department...and go from there

MLF

WEBABASSETT82

3 letter department code, initials, last name, year of birth

whats wrong with something like that? not using any info that is not normally available and very very very little chance of having username conflicts

just give them an employee number. simple. first 3 digits can identify the department, last 4 for the employee.

What about something with firstname and then some part of date of birth, people don't generally change their firstnames?

Maybe you could use first few characters of first name and then a portion of their DOB or employee number if there is one available.

e.g

Name John Doe
Employee # 51432678
DOB 01/01/1976

could be

joh678 or
jo0101

its a stupid idea to use things like DOB, SSN, etc in usernames. those are private unique identifiers and are often used for authorization purposes. Most companies ask for the last 4 digits of your ssn or your birthdate to verify you.

Quote:

---

we are constantly having to change usernames due to name changes.

---

Am I the only one who finds this strange?

People at your work change their names that frequently? Originally I thought you might have intended to mean that the people operating specific roles change... but your continued use of a unique and personalized unique identifier indicate otherwise.

Do not use their SSN, you are ONLY allowed to use this for their tax information and they can refuse its use in part or whole for anything else, especially as an identifier (hence the military uses Serial Numbers).

XTC is spot on for your situation... almost. He is spot on for what you've asked... unfortunately what you've asked is bad.

How will email accounts be handled? Do these users have two distinct authentication systems they need to go through? If so, won't that one also have to go through name changes "constantly"? If so, does it make sense for users to remember two different sets of authentication information? or well you use the first auth scheme to store the second? (ick) If the user only has one auth scheme... do they give out their email as [email protected] ? God, how degrading... "Yeah my company didn't even bother to learn my name."

How degrading every time you login. "Sometimes I feel like I'm not even a person, here locked away in my cube with no natural light for 8 hours a day. Oh a memo... *muttering* My new username is 4516025?? Tomorrow I bring the uzi instead of my normal PB&J."

Just make the username change process overly punctilious and be done with it. ;)

cheers,

catch

Quote:

---

Do not use their SSN, you are ONLY allowed to use this for their tax information ...

---

For years and years I thought I was one of the few on earth who knew this ( my brother, an accountant, had provided a hard copy of the Federal rules governing this. It was one of his pet peeves. )

It wasn't until the banks and other institutions ( insurance carriers, etc. ) got spanked by the Feds when identity theft got huge media attention that things changed. ( some used the SS number as account numbers. )


Although I believe there are some exceptions I believe catch is correct. I would discuss your plan with a knowledgeable tax attorney as well as local council before attempting something like this.

Quote:

---

(hence the military uses Serial Numbers)

---

They do? Did they get spanked too? In my day they used the SS number. ( I was in over 30 years ago. ) Any idea when that changed?

Why r u wasting time asking such a question.............. These things are not going to be added in any standardization formalities....Nor user name adoption technique is going to be standardized in very near future yet..... till we have so many discreet networks across the internet.

You have a problem to assign user names to all people of ur organization.. .. simply put use whatever is convenient to remember for your colleagues and for u to identify them.... take care of the rules and regulations so that nobody's confidential info is revealed.. and lo u have the solution.

Quote:

---

They do? Did they get spanked too? In my day they used the SS number. ( I was in over 30 years ago. ) Any idea when that changed?

---

I should have said us(ed.)/(es?) ;)

The US Army introduced Serial Numbers in WWI (I don't believe the Social Security system came into effect until the Great Depression.) and killed them during Vietnam. The problem was that under the McNamara project, minimal IQ requirements were dropped to meet manpower needs. Subsequently they switched from serial numbers to social security numbers... as it stands now I believe you get a social security number and a serial number, but the serial number never makes it to the dogtag and is used pretty much exclusively for internal tracking (as the serial number is more "intelligent" than the social is) However with everything being on computers now, more data can be stored and numbers don't need to be so smart... so really I have no idea what they are doing.

However, I do know that when you sign-up/are drafted you can give an Employer Identification Number (nine digit number, EIN) instead of your social.

cheers,

catch

All,

If I remember correctly, a social security number is not compulsory.

As stated by the Social Security Act:

Quote:

---

(B)(i) In carrying out the Commissioner's duties under subparagraph (A) and subparagraph (F), the Commissioner of Social Security shall take affirmative measures to assure that social security account numbers will, to the maximum extent practicable, be assigned to all members of appropriate groups or categories of individuals by assigning such numbers (or ascertaining that such numbers have already been assigned):

---

Numbers shall be assigned to the maximum practicable extent. Back when I lived in the States, I seem to remember having a couple of non-US colleagues who did NOT have an SSN.

To get back on topic though, I would agree that your employee ID is probably your best best for account names. Of course, this does not address the need for email addresses ...

Cheers,

BrainStop

Quote:

---

The US Army introduced Serial Numbers in WWI

---

Well, since I'm not as old as nihil this doesn't apply to me. :)

Quote:

---

The problem was that under the McNamara project, minimal IQ requirements were dropped to meet manpower needs.

---

Well, now I know how I got in.

Quote:

---

I do know that when you sign-up/are drafted ...

---

I don't recall any reference to any other numbers back then, guessing this did change over time though. ( hey, they now keep samples of DNA of everyone in the service, thus no more “ Unknown Soldiers” . ) But my biggest disappointment was that they took my draft card. I would have like to of had that as a souvenir.

I really don't want to hijack this thread so I won't go further into the “ draft “ subject.

I do want to commend catch on bringing up the SS number restrictions. ( I can't assign him APs at this time though ) I think this was extremely pertinent to this thread and something everyone in similar situations should be aware of. With the advent of computers ( years ago ) it was extremely easy to just use a unique identifier which was already assigned to an individual, so lazy people took the easy way. They had no forethought, no hindsight, and no cares about the laws which applied that no one was willing to enforce; .... until it bit everyone in the arse.

Does this scenario sound all too familiar??

Since I'm typing slow,

Quote:

---

I seem to remember having a couple of non-US colleagues who did NOT have an SSN.

---

Another good point, but is on topic. They were, as you said, “ non-US “.

I may be wrong here, this is my understanding, but let me give you this:

You work for a German company in Germany. They send you to the U.S. for a few months. You are still employed in Germany. Why would you have a U.S. SS number, or need it?

You are a citizen of India. You move to the U.S. You get a new job with a company based out of India. Because you are employed here you would need a SS number in the U.S., even if you never applied for citizenship.

Again, I won't go further with the merits of the SS system itself as it is not pertinent to the topic, but that may explain the above post.

As how it applies to this thread? How many companies have people with accounts who are employed outside of the U.S. ???

When you are creating account names, dont use a "format rule" that forces will to change acct name when user move between depts.

For example: suppose you are naming guys like SALE001, HR001, etc... some day a employee move from sales dept to HR dept... do you want to change his account?

I allways prefer a simple one:

Ennnnnn - for employees
Nnnnnnn - for non employees

here nnnnnn is a sequential number, starting from 1000 :)

easy, inst it?

(why not starting from 0001? because in one company i had soooo much problem when a lot of VIP were disputing the begining range (1-10).... )

Take care to not overlook morale as a cost to information systems.

Sure using an employee number might be more convenient for the MIS people, but like I said above... how will employees feel about this? There is a reason that prisons assign and use a number identifier rather than name... it dehumanizes you.

Just stick to a simple first.last / last.first / flast / fmlast, etc system. Users are people too.

cheers,

catch

PS. Yeah, I know I'd suck as a BOFH.

Edited to correct the typo of "moral" to "morale". ;)

You'd be surprised how quickly duplicates appear when you use these "never hit a duplicate formatted ID's" the OP suggested.

When I first started working here I inherited a database that used the first name initial, the first two letters of the last name and the last four of the SSN as an ID. When I had to rewrite the db I first had to check over the data prior to import, (it was a flat file rather than relational). I found 14 duplicate ID's in 4,500.....

A fun idea might be to let users pick their own login/email name. Clearly it would have to be unique (and nothing too offensive)... but beyond that, let 'em go hog wild.

This would solve all the problems... now I know some people might argue that the lack of predictable formatting or intelligence is a bad thing... but really how is it? Do you really need the user name to tell you anything? Most systems support a user description and with email addresses most people just click "add to address book" and "reply" I can't even remember the last time I wrote down an email address.

cheers,

catch

PS. Granted having users with email addresses like "[email protected]" isn't going to give you that faceless, IBM-style corporate image...

very good information posted on this topic. I will continue to think about the username format I will use. But you know what, I too have an everyday account that uses my SS as my username! I am not the one to talk or gossip, but there is a major education institution here in Houston, Texas that I use and that students use their Social Security Numbers as user ids. This whole time I did not care to think about this. Damn, how could I been such a fool. Oh well, I agree with user "catch" I would like to make usernames easy but unique for users. Not only do I need a format to benefit the department, but something to benefit the users and to cut down frustration. Email is not a problem. All accounts will be tied to this format [email protected]. I am still leaning towards the id format that I posted about.

catch,

[QUOTEnow I know some people might argue that the lack of predictable formatting or intelligence is a bad thing... but really how is it? .... that faceless, IBM-style corporate image[/QUOTE]

Speaking of that faceless IBM corporate image, they are not very predictable themselves. First of all, you need to know in which country the employee works (which is not always easy when your first level of sales is in Switzerland, your first line of support in the Netherlands, your second level of sales is in the UK, second level support in Canada and overall account management in the US ....), then you need to start guessing at the formatting.

I've seen the following so far:

firstname@<countrycode>.ibm.com
firstname.lastname@<countrycode>.ibm.com
<initials>lastname@...
lastname@...
lastname<initials>@...

Now granted, IBM has an online employee directory ... but it only works if you know the country where the employee is located.

Cheers,

BrainStop

PS = Yes, I spend a bunch of time dealing with IBM on a software product at the moment.

I don't know...it just seems to me that you are adding additional administrative work for yourself.

If you are going to come up with a naming convention, like HRFC1411 (Human Resources File Clerk + Last 4 of SSN), and then tie it to [email protected], you're not creating any less work, because when Betty marries Chef Boyardee, you'll be changing the email address to [email protected]!

I don't know what server OS you are using, but I use Windows 2003 strictly as a domain controller, and I have a Exchange Server that is a member of the domain. All of my logins are structured as follows:

[email protected]

That way, I only have to change an account 1 time and it changes all of them. For my legacy systems, they use first initial, middle initial, last initial, last 4 of SSN (or month and year of birth...I don't make use of even the last 4 mandatory).

In the case of duplicates (people with the same first/last) I go by tenure...

i.e.: I have two employees named Orville Redenbacher. I pull the personnel file on them both. The one that was hired first is [email protected]. The other one gets his middle name used: [email protected].

I also have a policy on name changes...I don't do them unless it is a Legal Name change. So when Ott down in accounting wants me to change his name from [email protected] to Ott.Spunkmeyer...I say "What's the name on your Social Security Card, cuz' that's the name I'm using, bro!

Quote:

---

Originally posted here by mrlucifer
hello people, quick question. I was wondering what was your favorite username format to use as a network administrator at a business. We are going through major transistions in our internal network and I am looking for a new way to identify users through the network and company. I really don't want to use first and last names because we are constantly having to change usernames due to name changes. I was thinking about this format:

Birthday 01/02/2005 SS#123-56-7890

username:027890



What do you think?

---

FIRST INITIAL-LAST INITIAL [dept or # sign] year of birth

Mike Johnson - Payroll - 1975

MJ#1975 or MJPR1975

awesome feedback. Hands down, I think I am going to stick with the day of birth and the last 4 characters of the Social Security. Its easy and unique and discreet. I can easily standarized this username across many systems and easily tie it a smart card. The department thing wouldnt work because I have many users that work in many departments. Lastname initials and firstname initials would be a big hassle because we get many request for last name changes. and the whole email username would not work at all because most of our systems have a 8 character limit length. no worky. One thing we do enforce is a 10 character password. People really hate that. lol Thanks guys for all the info. More feedback is appreciated. ***I still can't believe my school made my user id as my SS!" sh*t and i didn't even notice it.