<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Courier New; font-size: 10pt; color: #000000'>Jules, please ignore this request as all that is required is JS magic in login.tpl:<br><br> <script type="text/javascript"><br> bindEnter($('#passwordField'), function(){ submitform() });<br> function submitform() {<br> var uname = document.forms["login"].uname.value;<br> document.forms["login"].uname.value = uname.substring(uname.indexOf("\\")+1);<br> document.login.submit(); }<br> </script><br><span>-- <br>Thanks, Phil<span name="x"></span><br></span><br><hr id="zwchr"><blockquote style="border-left:2px solid rgb(16, 16, 255);margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><style>p { margin: 0; }</style><div style="font-family: Courier New; font-size: 10pt; color: #000000">Jules, a number of our test users have commented that it would be great if they were able to specify the same sign on credentials as they do for other systems. What is the difference you may ask? Well all other systems require DOMAIN\USERID and they are looking for consistency. They believe when rolled out there will be a lot of login failures as people will try to use the later format. How feasible would it be to add a parse routine to the code to strip the slash and domain from the login credentials ?<span><br><span></span>-- <br>Thanks, Phil<span></span><br></span><br></div><br>_______________________________________________<br>ZendTo mailing list<br>ZendTo@zend.to<br>http://mailman.ecs.soton.ac.uk/mailman/listinfo/zendto</blockquote><br></div></body></html>