Misi, We still have a good portion of our users on the Remedy User client, so we don't really have the option of relying on a web login dialog anytime soon. Thanks for the idea - something for me to keep in mind -
David David Durling University of Georgia -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Misi Mladoniczky Sent: Wednesday, May 25, 2011 3:44 AM To: arslist@ARSLIST.ORG Subject: Re: login name not friendly or recognizable Hi, With things explained a little further, I do not see that the custom authenticator would be able to solve your problem. You want the user to use the Unfriendly Name at Login, and you want to see the Friendly Name in all other places. You must do some additional things. You must swap the Unfriendly name to the Friendly name before it is sent to the AR Server. You can still keep the Unfriendly name for the authenticator by putting that into the extra Authentication-field that is normally not used. The technology to trap the login dialog differ between the native client and the web client. If you are using DevStudio, it is not possible create your own login dialog. Another problem is that the authenticator (AREA-plugin) is only called when the password-field is blank. That means that you have to store the actual password somewhere else... Could you not just use the Friendly name in all places in the AR System except one? That would be the actual login dialog on the web client, where you have some java-script-code to map the entered Unfriendly login name into the Friendly name used by the system? Best Regards - Misi, RRR AB, http://www.rrr.se Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10): * RRR|License - Not enough Remedy licenses? Save money by optimizing. * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs. Find these products, and many free tools and utilities, at http://rrr.se. > I didn't either, but thought I'd mention just in case! I don't think I > have the ability to do a custom authenticator like Misi suggested, and > know if it would work in our setup. > > Perhaps it would be an interesting enhancement allow for an alias to be > associated with Login Name for system timestamps - or maybe a server > setting that says "use Full Name". Though I guess that could present > auditing problems - > > David Durling > University of Georgia > > > From: Action Request System discussion list(ARSList) > [mailto:arslist@ARSLIST.ORG] On Behalf Of LJ LongWing > Sent: Tuesday, May 24, 2011 3:31 PM > To: arslist@ARSLIST.ORG > Subject: Re: login name not friendly or recognizable > > ** > Outside of writing a custom authenticator, as mentioned earlier, I don't > see that as an option. > > From: Action Request System discussion list(ARSList) > [mailto:arslist@ARSLIST.ORG] On Behalf Of David Durling > Sent: Tuesday, May 24, 2011 12:04 PM > To: arslist@ARSLIST.ORG > Subject: Re: login name not friendly or recognizable > > ** > At the login prompt in Brien's case the user will be typing in the > "friendly" name, while the alias in field 117 is used behind the scene. > > That's okay if you don't mind the users using the "friendly" name at > login. But it does bring up a concern of mine: > > I'd like a way to use the external alias at the login prompt (since that's > the login our users are familiar with) without having it be the value is > stamped on fields. Otherwise, I'm looking at the same issue Brien > mentioned of creating > extra fields (and an extra line for each diary field entry) to show who > updated the case. Any other ideas on how to handle that? > > David Durling > University of Georgia > ARS 7.5 > > From: Brien Dieterle [mailto:brien.diete...@cgcmail.maricopa.edu] > Sent: Tuesday, May 24, 2011 11:09 AM > To: arslist@ARSLIST.ORG > Cc: David Durling > Subject: Re: login name not friendly or recognizable > > Yes, this looks perfect. I'm so glad I wasn't the only one clueless to > its existence :-). > > We just went through a Login Name migration using Misi's nifty tool > rrrLoginConv<https://www.rrr.se/cgi/tools/main#rrrLoginConv>. Now I have > to find downtime to run that tool again to replace the unfriendly name > with a friendly one, but it should work great! > > Thanks!! > > Brien > > On 5/24/2011 6:30 AM, David Durling wrote: > > If I understand, field 117 only works with external authentication (it is > the login name on the external system). At least that's how we use it. > So it should help Brien if that's his situation. > > > > David > > > > -----Original Message----- > > From: Action Request System discussion list(ARSList) > [mailto:arslist@ARSLIST.ORG] On Behalf Of John Sundberg > > Sent: Tuesday, May 24, 2011 8:16 AM > > To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> > > Subject: Re: login name not friendly or recognizable > > > > That is a sweet option -- I like it!!! > > > > Well done BMC... (Actually Remedy if 5.1.2 ???) > > > > Surprisingly I have never heard about it. > > > > Is there weird fallout from using it??? Like $USER$ is the authenticated > value? Or ??? > > > > -John > > > > > > > > On May 23, 2011, at 6:57 PM, LJ LongWing wrote: > > > > Brien, > > You can add a field to the User form (forget the ID off hand) that allows > > you to specify ABC013251 is an alternate ID for user smith.john, but leave > > smith.john as the login ID....they would be able to authenticate with the > > alternate ID, but the username would still be populated into last mod, > > diary, etc....the full details and specs are in the documentation. > > > > -----Original Message----- > > From: Action Request System discussion list(ARSList) > > [mailto:arslist@ARSLIST.ORG] On Behalf Of Brien Dieterle > > Sent: Monday, May 23, 2011 4:28 PM > > To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> > > Subject: login name not friendly or recognizable > > > > How do you all deal with environments where your Login Name is not > > "Friendly", such as "ABC013251"? We are moving from using "lastname" > > (generally) to this pseudo random ID. Naturally, people do not like > > this appearing in the Last Modified By, Submitted By, Assigned To, and > > other fields that need Login Names. There are enough fields and enough > > forms that I'd really like to avoid adding extra fields to store/display > > this information all over the place. Do you Listers have any > > recommendations or best practices for this situation? I was considering > > a shared button/workflow that pops up a search tool to let users paste > > in an ID and return the details including Full Name, etc. A directory > > lookup, basically. Any better ideas out there? > > > > Thanks! > > > > Brien >
