My company is changing the way they're creating login IDs in active directory. They used to all be lowercase, but now users will be added with mixed case IDs. We previously stored only login ID in our security data model, and these were always lower case, but we've been testing a mixed domain community and a proof of concept security data model in SQL Server stores "Domain/login" as the user ID. Capital D.
When I tested section access using USERID and PASSWORD against this data source, I had to log into the secured QlikView document with "Domain/login" and not "domain/login". This was surprising as the PASSWORD field is not case sensitive when using this method.
Will NTNAME face the same restriction and fail resolving against the user's login name if it is case sensitive?
Thank you,
Richard
