Windows Authentication & Network ID presentation
This recently came to my attention:
With windows authentication, I have a user who (when accessing from one part of the world) is presented as:
DOMAINNAME\auser1234
and accessing from another part of the network / world, is presented to gemini as:
DOMAINNAME\AUSER1234
Now, that user is in the user table TWICE. Clearly, I don't want this behavior.
To ignore case in user-ID for WINDOWS AUTHENTICATION ONLY, both for validation and registration / creation, which stored procedures should I look at? I'm assuming this should be enough - to introduce case-agnostic windows authentication in the SPROCS.
Thanks,
Yarko
|
yarkot
· 1 |
|
| Thursday, March 9, 2006, 5:41:44 PM | |




