Bill Witherspoon wrote: >> Yes please test Win Auth. Before we make changes to any of the code we need >> to insure Win Auth works. The code assoicated with 'port' in dbMsSQL.py >> (Dabo's side of the connection) is not used and I think everyone forgot to >> remove it. >> >> I don't have psmssql.py setup for windows. Can anyone explain what is >> replacing the Linux FreeTDS libs? What ever is replacing FreeTDS should >> contain the port information settings. > > Just finished testing and I cannot get Win Auth to work. I've tried all > the variations that I can think of: > > user='billw', user='Emcorp\billw', user='[EMAIL PROTECTED]', user='\:', > user='\\', etc.
This is better, but would helpful now and really nice for posterity if you would give us real code, and the real results. > > (Emcorp being our domain) along with appropriate passwords (and no > password, etc.) > > I tried these variations with the server set to Mixed and to Win Auth > only. The good news is that removing the port makes incorrect logins > fail in two seconds, where I was waiting for a time out before. ;-) Win and Mixed are the same thing when it comes to Win. If you are trying for win, I would set the server to Win just to make sure you don't accedently connect via SQL auth and confuse everyone. > > I believe Carl suggested that using Win Auth, simply "knocking" on the > door should prompt Sql to check if the "knocker" has the appropriate > credentials. I agree with this, but suspect that pymssql is not set upreally, > to accommodate this. If you supply no user it defaults to "sa" for > example. (I did override this behavior as well, no dice). It would seem > to me that if the capability existed it would be in the pymssql > connection parameters as well, ie: > > def connect(dsn = None, user = "sa", password = "", host = ".", database > = "master"): > > would be: > > def connect(dsn = None, user = "sa", password = "", host = ".", database > = "master", authtype = "SQL"): > > or something like that. Dig up the URLs I posted to the code that pymssql relies on. I am pretty sure the 'flag' for win auth is the slash in the user name. pretty sure that is the only thing in the username that actually gets used. I get the feeling the author of that code didn't understand how Win auth worked, and fooled himself into thinking a user/pw was needed. (all on feeling, never did look that deep into the code) and a friend thinks you can connect using other credentials that your current login, which would kinda imply you can pass a user/pw, which would kinda imply you could pass your current one. so in case it wasn't clear, I really have no clue :) If it was a back slash, you will need to escape it by putting 2 slashes: >>> print "\\a" \a forward slash is OK by itself: >>> print "/a" /a > > Would it be worth trying to get in touch with the pymssql author? yes. but I would first get better at posting code and results :) > I > would do it if asked, but I suspect Ed or another Dabo developer might > get better traction. So far I think you are the only one with a 'working' setup, so you are going to be the most qualified. Also, I seem to remember getting no response when I found the unicode problem. don't actually remember sending anything either... Carl K _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/dabo-users/[EMAIL PROTECTED]
