Gemini Community Support Site

This Gemini community support site can be used to find solutions to product issues. You can log in using Open Id, Google Profile and even Facebook. Feel free to ask a question or browse FAQs and documentation. Product tour videos are also available along with how-to videos demonstrating key Gemini capabilities.




Windows Authentication & Network ID presentation

web-app

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:

  DOMAIN
NAME\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
yarkot
Replies (6)
helpful
0
not helpful

Are you running on case sensative SQL database?


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

If I said "Huh?!"  would that answer your question?

It's a server installed out of box w/ defaults;

It's a Gemini database, based on Gemini install *.msi's (ok - now, upgrades since 1.8*).

I suppose I should wade thru the SQLServer docs to see how / where I affect case sensitivity of a database, and if I can affect that easily on an existing.

Any pointers apreciated...

Yarko.


yarkot
· 1
yarkot
helpful
0
not helpful

Open SQL Enterprise Manager, select your database and right click -> Properties.

On the general tab, you should see "Collation name:".

What is the value of it? If that does not contain CI then you might be running case sensative.


Mark Wing
· 9108
Mark Wing
helpful
0
not helpful

They all contain "CI"  (I have several Gemini instances, sharing - thru a view - the users table from the "main" Gemini).


yarkot
· 1
yarkot
helpful
0
not helpful

The stored procedure that is run to check if a user exists or not is: gemini_getuserid.

As far as I can remember you have amended this to create your users. Check the procedure or send us the code.


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

The modification I made was for my 2.0.3 upgrade (which I have not yet deployed).

The issue mentioned here is in a "stock" 1.9.1 installation.  In this instance, the user table belongs to the database in question (the other 1.9.1 installations have had their user table replaced w/ a view that points back to this "master" user table with a simple:

create view users as select * from Maingemini19_1.dbo.users

Regards,

Yarko


yarkot
· 1
yarkot