Re: login name not friendly or recognizable
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:
Re: login name not friendly or recognizable
I remember thinking the same thing you did when I read that sentence in the docs in the past, so I understand! David From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Brien Dieterle Sent: Tuesday, May 24, 2011 8:08 PM To: arslist@ARSLIST.ORG Subject: Re: login name not friendly or recognizable ** Dang, I was reading what I wanted to believe, I suppose. Brien On 5/24/2011 1:05 PM, David Durling wrote: ** Sorry, it may have sounded like I was talking SSO - but I meant not having to use specifically the "Login Name" field contents at the prompt David Durling University of Georgia From: David Durling Sent: Tuesday, May 24, 2011 2:39 PM To: 'arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>' Subject: RE: login name not friendly or recognizable Yes, the Authentication Login Name is used for authentication, but that's "behind the scenes" - the user still has to type the Remedy Login Name in the login dialog box - and that's what I don't want them to have to do. We're been using this using this for a while, with a mix of accounts - some local Remedy passwords, some against LDAP. The LDAP users do have to type in whatever is in the Login Name field on the user form in order to log in. But maybe there's some other way of configuring this I've missed - David From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Brien Dieterle Sent: Tuesday, May 24, 2011 2:32 PM To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> Subject: Re: login name not friendly or recognizable ** That's not how I read it, although I haven't had a chance to test this. The docs say this, specifically (emphasis my text). If the Authentication Login Name (Unfriendly Name) field is present on the User form, the value contained in this field is used for authentication instead of the name entered in the User Name field (Friendly Name) in the Login dialog box. In our case we will be using single-signon (kerberos) with our unfriendly Active Directory account name. So this should work perfectly for both of us, right? Brien On 5/24/2011 11:04 AM, David Durling wrote: ** 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 Sent: Tuesday, May 24, 2011 11:09 AM To: arslist@ARSLIST.ORG<mailto: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 IDthey would be able to authenticate with the alternate ID, but the username would still be populated into last mod, diary, etcthe 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<m
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 usi
Re: login name not friendly or recognizable
**
Dang, I was reading what I wanted to believe, I suppose.
Brien
On 5/24/2011 1:05 PM, David Durling wrote:
**
Sorry, it may have sounded like I was talking SSO
– but I meant not having to use specifically the “Login
Name” field contents at the prompt
David Durling
University of Georgia
From: David Durling
Sent: Tuesday, May 24, 2011 2:39 PM
To: 'arslist@ARSLIST.ORG'
Subject: RE: login name not friendly or
recognizable
Yes, the Authentication Login Name is used for
authentication, but that’s “behind the scenes” - the user
still has to type the Remedy Login Name in the login dialog
box – and that’s what I don’t want them to have to do.
We’re been using this using this for a while,
with a mix of accounts – some local Remedy passwords, some
against LDAP. The LDAP users do have to type in whatever is
in the Login Name field on the user form in order to log in.
But maybe there’s some other way of configuring
this I’ve missed –
David
From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG]
On Behalf Of Brien Dieterle
Sent: Tuesday, May 24, 2011 2:32 PM
To: arslist@ARSLIST.ORG
Subject: Re: login name not friendly or recognizable
**
That's not how
I read it, although I haven't had a chance to test this. The
docs say this, specifically (emphasis my text).
If the Authentication Login Name (Unfriendly
Name) field is present on the User form, the value
contained in this field is used for authentication instead of
the name entered in
the User Name field (Friendly Name) in the Login
dialog box.
In our case we will be using single-signon
(kerberos) with our unfriendly Active Directory account name.
So this should work perfectly for both of us, right?
Brien
On 5/24/2011 11:04 AM, David Durling wrote:
**
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
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. 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
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
Re: login name not friendly or recognizable
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 IDthey would be able to authenticate with the alternate ID, but the username would still be populated into last mod, diary, etcthe 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 ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org<http://www.arslist.org> attend wwrug11 www.wwrug.com<http://www.wwrug.com> ARSList: "Where the Answers Are" __
Re: login name not friendly or recognizable
Sorry, it may have sounded like I was talking SSO - but I meant not having to use specifically the "Login Name" field contents at the prompt David Durling University of Georgia From: David Durling Sent: Tuesday, May 24, 2011 2:39 PM To: 'arslist@ARSLIST.ORG' Subject: RE: login name not friendly or recognizable Yes, the Authentication Login Name is used for authentication, but that's "behind the scenes" - the user still has to type the Remedy Login Name in the login dialog box - and that's what I don't want them to have to do. We're been using this using this for a while, with a mix of accounts - some local Remedy passwords, some against LDAP. The LDAP users do have to type in whatever is in the Login Name field on the user form in order to log in. But maybe there's some other way of configuring this I've missed - David From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Brien Dieterle Sent: Tuesday, May 24, 2011 2:32 PM To: arslist@ARSLIST.ORG Subject: Re: login name not friendly or recognizable ** That's not how I read it, although I haven't had a chance to test this. The docs say this, specifically (emphasis my text). If the Authentication Login Name (Unfriendly Name) field is present on the User form, the value contained in this field is used for authentication instead of the name entered in the User Name field (Friendly Name) in the Login dialog box. In our case we will be using single-signon (kerberos) with our unfriendly Active Directory account name. So this should work perfectly for both of us, right? Brien On 5/24/2011 11:04 AM, David Durling wrote: ** 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 Sent: Tuesday, May 24, 2011 11:09 AM To: arslist@ARSLIST.ORG<mailto: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 IDthey would be able to authenticate with the alternate ID, but the username would still be populated into last mod, diary, etcthe 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
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 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 IDthey would be able to authenticate with the alternate ID, but the username would still be populated into last mod, diary, etcthe 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 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 ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" -- John Sundberg Kinetic Data, Inc. "Building a Better Service Experience" Recipient of: WWRUG10 Best Customer Service/Support Award WWRUG09 Innovator of the Year Award john.sundb...@kineticdata.com 651.556.0930 I www.kineticdata.com ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are
Re: login name not friendly or recognizable
Yes, the Authentication Login Name is used for authentication, but that's "behind the scenes" - the user still has to type the Remedy Login Name in the login dialog box - and that's what I don't want them to have to do. We're been using this using this for a while, with a mix of accounts - some local Remedy passwords, some against LDAP. The LDAP users do have to type in whatever is in the Login Name field on the user form in order to log in. But maybe there's some other way of configuring this I've missed - David From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Brien Dieterle Sent: Tuesday, May 24, 2011 2:32 PM To: arslist@ARSLIST.ORG Subject: Re: login name not friendly or recognizable ** That's not how I read it, although I haven't had a chance to test this. The docs say this, specifically (emphasis my text). If the Authentication Login Name (Unfriendly Name) field is present on the User form, the value contained in this field is used for authentication instead of the name entered in the User Name field (Friendly Name) in the Login dialog box. In our case we will be using single-signon (kerberos) with our unfriendly Active Directory account name. So this should work perfectly for both of us, right? Brien On 5/24/2011 11:04 AM, David Durling wrote: ** 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 Sent: Tuesday, May 24, 2011 11:09 AM To: arslist@ARSLIST.ORG<mailto: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 IDthey would be able to authenticate with the alternate ID, but the username would still be populated into last mod, diary, etcthe 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 id
Re: login name not friendly or recognizable
**
That's not how I read it, although I haven't had a chance to test
this. The docs say this, specifically (emphasis my text).
If the Authentication Login Name (Unfriendly Name)
field is present on the User form, the value
contained in this field is used for authentication instead of the
name entered in
the User Name field (Friendly Name) in the Login dialog
box.
In our case we will be using single-signon (kerberos) with our
unfriendly Active Directory account name. So this should work
perfectly for both of us, right?
Brien
On 5/24/2011 11:04 AM, David Durling wrote:
**
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. 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
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 IDthey would be able to authenticate with the
alternate ID, but the username would still be populated into last mod,
diary, etcthe 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
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
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 IDthey would be able to authenticate with the alternate ID, but the username would still be populated into last mod, diary, etcthe 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 ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org<http://www.arslist.org> attend wwrug11 www.wwrug.com<http://www.wwrug.com> ARSList: "Where the Answers Are" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org<http://www.arslist.org> attend wwrug11 www.wwrug.com<http://www.wwrug.com> ARSList: "Where the Answers Are" -- John Sundberg Kinetic Data, Inc. "Building a Better Service Experience" Recipient of: WWRUG10 Best Customer Service/Support Award WWRUG09 Innovator of the Year Award john.sundb...@kineticdata.com<mailto:john.sundb...@kineticdata.com> 651.556.0930 I www.kineticdata.com<http://www.kineticdata.com> ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org<http://www.arslist.org> attend wwrug11 www.wwrug.com<http://www.wwrug.com> ARSList: "Where the Answers Are" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org<http://www.arslist.org> attend wwr
Re: login name not friendly or recognizable
Hi, In that case it should be easy to write your own authenticator that just goes back to the User-form, thus allowing you to make use of the 117 functionality. 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. > David, > Just read up on field 117 and you are correct, only used when using > external > authentication... > > -Original Message- > From: Action Request System discussion list(ARSList) > [mailto:arslist@ARSLIST.ORG] On Behalf Of David Durling > Sent: Tuesday, May 24, 2011 7:30 AM > To: arslist@ARSLIST.ORG > Subject: Re: login name not friendly or recognizable > > 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 > 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 IDthey would be able to authenticate with the > alternate ID, but the username would still be populated into last mod, > diary, etcthe 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 > 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 > > > ___ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" > > > ___ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" > > > -- > John Sundberg > > Kinetic Data, Inc. > "Building a Better Service Experience" > Recipient of: > WWRUG10 Best Customer Service/Support Award > WWRUG09 Innovator of the Year Award > > john.sundb...@kineticdata.com > 651.556.0930 I www.kineticdata.com > > > ___ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" > > > ___ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" > > ___ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" > ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
Re: login name not friendly or recognizable
David, Just read up on field 117 and you are correct, only used when using external authentication... -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of David Durling Sent: Tuesday, May 24, 2011 7:30 AM To: arslist@ARSLIST.ORG Subject: Re: login name not friendly or recognizable 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 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 IDthey would be able to authenticate with the alternate ID, but the username would still be populated into last mod, diary, etcthe 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 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 ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" -- John Sundberg Kinetic Data, Inc. "Building a Better Service Experience" Recipient of: WWRUG10 Best Customer Service/Support Award WWRUG09 Innovator of the Year Award john.sundb...@kineticdata.com 651.556.0930 I www.kineticdata.com ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
Re: login name not friendly or recognizable
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 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 IDthey would be able to authenticate with the alternate ID, but the username would still be populated into last mod, diary, etcthe 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 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 ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" -- John Sundberg Kinetic Data, Inc. "Building a Better Service Experience" Recipient of: WWRUG10 Best Customer Service/Support Award WWRUG09 Innovator of the Year Award john.sundb...@kineticdata.com 651.556.0930 I www.kineticdata.com ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
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 IDthey would be able to authenticate with the alternate ID, but the username would still be populated into last mod, diary, etcthe 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 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 ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" -- John Sundberg Kinetic Data, Inc. "Building a Better Service Experience" Recipient of: WWRUG10 Best Customer Service/Support Award WWRUG09 Innovator of the Year Award john.sundb...@kineticdata.com 651.556.0930 I www.kineticdata.com ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
Re: login name not friendly or recognizable
Its been around for a few versions.. 5.1.2 if I am not mistaken.. Joe -Original Message- From: Brien Dieterle Sent: Monday, May 23, 2011 7:01 PM Newsgroups: public.remedy.arsystem.general To: arslist@ARSLIST.ORG Subject: Re: login name not friendly or recognizable Wow. Documentation huh? What's that? I never suspected a feature like this was available. Awesome. Thanks!! Brien On 5/23/2011 3: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 IDthey would be able to authenticate with the alternate ID, but the username would still be populated into last mod, diary, etcthe 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 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 ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
Re: login name not friendly or recognizable
Wow. Documentation huh? What's that? I never suspected a feature like this was available. Awesome. Thanks!! Brien On 5/23/2011 3: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 IDthey would be able to authenticate with the alternate ID, but the username would still be populated into last mod, diary, etcthe 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 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 ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
Re: login name not friendly or recognizable
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 IDthey would be able to authenticate with the alternate ID, but the username would still be populated into last mod, diary, etcthe 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 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 ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
