Rick, Maybe.
ARS lets use "authenticate" as a different user name than what the user enters in the Login Name field via the 'Authentication Login Name' field on the User form. So you could use that feature to set the employee ID number as the authentication user name and leave the ARS 'Login Name' field the string (rickw). This may be strange for the users, but they likely will prefer the English user names to the all digits anyways. Anyways.. that may be an option for you. -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. On Fri, Mar 7, 2008 at 4:41 PM, Rick Westbrock <[EMAIL PROTECTED]> wrote: > ** > > > Happy Friday, hopefully someone out there has run into this issue already > and can offer some advice. Our company is getting close to implementing ITIM > (IBM Tivoli Identity Management) for the enterprise which means that instead > of logging in with my name (rickw) I will be forced to log into the domain > with my employee ID number (7-digit integer). > > Since we are using Active Directory to authenticate users into Remedy > (including guest users who may submit a new support request using the > mid-tier) this is going to wreak havoc with our system. A lot of it can be > overcome by using shadow fields to hold the username and populating them > with a lookup based on employee ID number. All workflow that references the > USER keyword will be affected so there is going to be a lot of work involved > to get compliant. The biggest drawback to me is that the default diary field > prepend of date/time and username will now show a 7-digit number instead of > a username; I'll be forced to add a filter to every form that has a diary > field to append the user's name to the end of every diary entry. > > But wait, it gets better. How you may ask? In two ways: first we have > existing temporary employees who don't have a company issued ID number and > when they convert to becoming a regular employee they will get a number. At > that time they will have to start logging into the domain & Remedy with > their number instead of their name. All workflow concerns aside this means > that every time someone converts I will have to go back and update all > existing data to change their user name into their number. I have used a > utility in the past to do that as a one-time process for two users when we > first changed Remedy to cross-ref blank passwords to AD but this will be an > ongoing battle. Each time I will also have to determine which forms to > update based on the user's job function. > > The second big problem is that existing users will continue to use their > name to log in for several months but as of some cutoff date (TBD) all new > users will only be issued an employee ID but no login name. This means that > I will somehow have to account for a mixed user base where some people log > in with their name and others with their number. > > > If anyone has run into a similar situation in the past I would love to hear > from you, either on- or off-list. Even if you haven't personally been > involved with such an endeavor I really value the experience of everyone on > the list so feel free to chime in with your thoughts. > > > Thanks in advance, > > Rick > > > _________________________________ > Rick Westbrock > PETCO Store Systems Engineer > [EMAIL PROTECTED] _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
