1 of 1 people found this helpful
This has been a point of confusion for many years...but basically what your problem is is that you want them to log on using the alias, but have Remedy use the value in field 101, and that's not the way it works. The way it works is that they log in using the ID in 101, but the AREA uses the name in 117 instead...so if the requirement is that they log into EVERYTHING using A1266673, then that needs to be in 101, and the alias is of no use to you...but if you still want them to log onto Remedy using first.last, your current setup works fine...they can provide first.last in their username field...provide their PW for AXXXX, and remedy will authenticate them just fine. If however they need to log on with the AXXXX ID...I would recommend looking at RRR LoginConv (probably not quite the correct name)...but it will convert all of your logins from A to B for you.
Thanks for your inputs.
I was using the incorrect field (117) for login and hence it was not working. We tried logging in with 101 and it worked. I also verified plugin logs and it confirmed that when user logs in using firstname.lastname (remedy login name), the AREA plugin actually calls the TDS with the "Authentication Login Name" of the user.
This would meet our requirements Thanks again for all your help and support.