In my environment (university Computing Science department) the customers would be users, and, I imagine, they would (I know I would) rather log in using their short user id rather than their long-winded email address. I've looked at CustomerCreateAccount.dtl in an attempt to create a login page that separates Login from Email. I noticed that there was a "Login" section that had been commented out. I reinstated it, changing value="$Data{"UserEmail"}" to value="$Data{"UserLogin"}". Given this section of code in customer.pl if (!$GetParams{UserLogin}) { $GetParams{UserLogin} = $GetParams{UserEmail}; } I expected it to work. But it didn't. Customer accounts are still created with the email address being used for the login. Can it easily be made to work, or was the section in CustomerCreateAccount.dtl commented out for a good reason? Jim
Hi Jim, On Tue, Mar 11, 2003 at 12:01:46PM +0000, Jim Wight wrote:
In my environment (university Computing Science department) the customers would be users, and, I imagine, they would (I know I would) rather log in using their short user id rather than their long-winded email address.
I've looked at CustomerCreateAccount.dtl in an attempt to create a login page that separates Login from Email. I noticed that there was a "Login" section that had been commented out. I reinstated it, changing value="$Data{"UserEmail"}" to value="$Data{"UserLogin"}".
Sorry, the field name is wrong. Change it to: [...] <tr> <td>$Text{"Login"}: </td> <td> </td> </tr> [...] -=> name="Login"! And is should work. Jim, do you have all your customer-users in a central database or ldap directory? This would save you a lot of time and customer-user questions, because they don't need to create a new account and they don't need to set a new password. -=> OTRS is able to use external customer user (see http://otrs.org/pages/index.pl?Action=Ext&Site=Docu/customer.html - this also works in OTRS 1.0 but in OTRS 1.1 much better)
Jim
Martin -- Martin Edenhofer - <martin at edenhofer.de> - http://martin.edenhofer.de/ -- "There are two major products that come out of Berkeley: LSD and Unix. We don't believe this to be a coincidence." -- Jeremy S. Anderson
Martin Edenhofer writes:
I've looked at CustomerCreateAccount.dtl in an attempt to create a login page that separates Login from Email. I noticed that there was a "Login" section that had been commented out. I reinstated it, changing value="$Data{"UserEmail"}" to value="$Data{"UserLogin"}".
Sorry, the field name is wrong. Change it to:
[...] <tr> <td>$Text{"Login"}: </td> <td> </td> </tr> [...]
-=> name="Login"! And is should work.
That's what I had. I omitted to mention that I had changed from 'name="Email"' to 'name="Login"' too. I created two users, and both Logins came out as the email address. Without changing anything, I've tried again, and this time the Login is what I entered in the Login box. C'est la vie.
Jim, do you have all your customer-users in a central database or ldap directory? This would save you a lot of time and customer-user questions, because they don't need to create a new account and they don't need to set a new password.
We authenticate our departmental Linux logins against the campus Windows Active Directory using the Linux pam_krb5 module. Does that mean there is hope? I don't actually know much about the Windows AD. Jim
On Tue, Mar 11, 2003 at 02:30:50PM +0000, Jim Wight wrote:
Jim, do you have all your customer-users in a central database or ldap directory? This would save you a lot of time and customer-user questions, because they don't need to create a new account and they don't need to set a new password.
We authenticate our departmental Linux logins against the campus Windows Active Directory using the Linux pam_krb5 module. Does that mean there is hope? I don't actually know much about the Windows AD.
well, in this case you need a new authentication module which uses pam -- Regards, Wiktor Wodecki
participants (3)
-
Jim Wight -
Martin Edenhofer -
Wiktor Wodecki