Users can't connect to SOS - "hidden" passwords?

[kewlgeek]

Hello,

I have installed the trial version of SOS for my department to try it out and see if it works for us. I have no trouble logging into SOS from another machine using the Client software. However other users cannot connect. The message they are getting is "Invalid password - Login failed". All passwords are blank because our VSS servers use Windows authentication to validate users. The service was set up to use my domain\username and they may be why I can connect myself. Not sure what I'm doing wrong.

Here is the log:

4/1/2005 2:23:15 PM - ****************************************************
4/1/2005 2:23:15 PM - SourceOffSite Server 4.1 Professional - With Cryptography

4/1/2005 2:23:15 PM - CurrentCulture is en-US.

4/1/2005 2:23:16 PM - Server Information
4/1/2005 2:23:16 PM - Operating System: Microsoft Windows XP Professional
4/1/2005 2:23:16 PM - Service Pack: 1.0
4/1/2005 2:23:16 PM - OS Version: 5.1.2600
4/1/2005 2:23:16 PM - Locale: Ox0409
4/1/2005 2:23:16 PM - OSLanguage: 1033
4/1/2005 2:23:16 PM - Total Physical Memory: 254.42 MB
4/1/2005 2:23:16 PM - Time Zone: (GMT-06:00) Central Time (US & Canada)
4/1/2005 2:23:16 PM -
4/1/2005 2:23:16 PM - SSAPI.dll Information:
4/1/2005 2:23:16 PM - Location: file:///C:/Program Files/SourceOffSite Server/Interop.SourceSafeTypeLib.DLL
4/1/2005 2:23:16 PM - DisplayName: Interop.SourceSafeTypeLib, Version=5.1.0.0, Culture=neutral, PublicKeyToken=null
4/1/2005 2:23:16 PM -
4/1/2005 2:23:16 PM - Started at 4/1/2005 2:23:16 PM

4/1/2005 2:23:16 PM - General logging level is Error. Method logging is Disabled.

4/1/2005 2:23:16 PM - Number of licenses configured: 10

4/1/2005 2:23:16 PM - $/ deploy to \\\\gatekar02.americas.cpqcorp.net\\SourceOffSite
4/1/2005 2:23:16 PM - SourceSafe Initialization file(s) located at:
4/1/2005 2:23:16 PM - \\vsshou02\finrefit-ss\srcsafe.ini

4/1/2005 2:23:16 PM - GATEKAR02 is attempting to listen for connections on secure port 8081
4/1/2005 2:23:16 PM - GATEKAR02 is attempting to listen for connections on unsecure port 8080


4/1/2005 2:23:16 PM - Waiting for a connection....secure = False
4/1/2005 2:23:16 PM - Waiting for a connection....secure = True
4/1/2005 2:24:16 PM - Connection accepted from 16.101.122.66:2033 on local address 16.101.121.239:8081, session id is 1.
4/1/2005 2:25:45 PM - Connection accepted from 16.101.122.66:2039 on local address 16.101.121.239:8081, session id is 2.
4/1/2005 2:25:50 PM - Unable to backup C:\Program Files\SourceOffSite Server\sossvr.prp
4/1/2005 2:25:50 PM - 2: Exception during Login: Invalid password
4/1/2005 2:25:50 PM - 2: Invalid password
4/1/2005 2:26:03 PM - Connection accepted from 16.101.122.66:2040 on local address 16.101.121.239:8081, session id is 3.
4/1/2005 2:26:24 PM - Connection accepted from 16.101.122.66:2041 on local address 16.101.121.239:8081, session id is 4.
4/1/2005 2:26:30 PM - 4: Exception during Login: Invalid password
4/1/2005 2:26:30 PM - 4: Invalid password
4/1/2005 2:26:36 PM - Connection accepted from 16.101.122.66:2042 on local address 16.101.121.239:8081, session id is 5.
4/1/2005 2:26:59 PM - 5: Exception during Login: Invalid password
4/1/2005 2:26:59 PM - 5: Invalid password
4/1/2005 2:27:03 PM - Connection accepted from 16.101.122.66:2043 on local address 16.101.121.239:8081, session id is 6.
4/1/2005 2:27:10 PM - 6: Exception during Login: Invalid password
4/1/2005 2:27:10 PM - 6: Invalid password
4/1/2005 2:34:58 PM - Connection accepted from 16.101.122.66:2095 on local address 16.101.121.239:8081, session id is 7.
4/1/2005 2:35:01 PM - 7: Exception during Login: Invalid password
4/1/2005 2:35:01 PM - 7: Invalid password


Thanks for your help.

Karin

[kewlgeek]

Okay, this is weird. The reason it worked for me is because I was using my account to start the service. If I change it to use a different account then it didn't work for me. But I found a kudge the made it work for me.

I changed the service to start as me. Then I changed my password in the tools menu of SOS. This only works if I use my NT password. If I don't then other users were able to sign onto VSS as me!

Then I change the service to a different user. After that I could log on using my NT password. In VSS itself I continue to logon with a blank password because I believe behind the scenes it's getting my NT password.

Tell me I won't have to go through this process for every user! The problem seems to exist because of the way our VSS administration uses our Windows NT passwords behind the scenes.

Thanks,
Karin

[lbauer]

SourceOffSite doesn't support Windows Authentication. Each user needs a VSS username and password. If network authentication is enabled in the VSS Admin tool and you use a user's account for the SOS Server service, then anyone can log in as you -- because the SOS Service is running as you.

When you "changed" your password using SOS, you actually created a password in VSS.

Anyway, as you've seen, it's quite confusing.

I'd suggest creating passwords for each VSS user. If you still encounter errors, you might need to delete and recreate each user in VSS.

[kewlgeek]

Our VSS GUI interface doesn't let us change our password. In SOS, the only password that I could change it to in SOS was my current NT password, but I was only able to do that after I got logged on to SOS, which was only after setting the service start-up user name to my own. Therein is the problem. I can't change each user to the startup user just so they can log on and from there change their passwords. I'm not a VSS administrator here at my company. I work for a very large corporation and I don't have privileges to change other users' passwords.

Seems to be a catch-22. Looks like we won't be able to purchase SOS for our use because of this issue.