Thread: Unable to Authenticate with WSI

We have just installed WSI on a test server and are having some trouble authenticating. In your documentation I found that is says "you must use the SuperAdmin Email and HASHED Password from the master AspDotNetStorefront database".

How do I retrieve the raw hash from the database? If I copy the hash from the field in MS SQL Management Studio I get a butchered string of characters.

That 'butchered string' is what it's looking for. You can either use that, or just disable the WSE3 authentication and enter the password in plain text (not recommended if you're retrieving order or customer info).

Sorry, I realize I worded that pretty badly. Afterall a hash is, by definition, a butchered string of characters :-P When I said butchered string, I meant that it doesn't look like a raw hash.

For example, here is just a small part of it...

?????!?Z# t??fL??/?

I'm not sure what kind of hash you are using but it doesn't look like what I'm used to seeing from MD5 hashes.

Yeah that'll happen sometimes unfortunately. You can end up with a password that works perfectly for the standard admin login but just won't work through WSE3. It's something with WSE3 authentication in general.

There are 2 things to try with that - first, copy the hashed password in to Notepad first and THEN into the password field. There's some kind of hidden characters in there sometimes that doing that strips out. If that doesn't work, you can actually just reset the password and try with the new hashed value. I've had it before that it took several tries to get one that worked.

I think we're planning on getting away from WSE3 here eventually (Microsoft is), hopefully this'll go away then.

Thank you Scott. That is unfortunate We will try this.

I am ready to hang myself over getting this to work with simrun commander, I've reset the password 40 times, I run a query in "query express" to see the hashed the password, I copy/paste it, tried it straight, and using the notepad step mentioned above, and nothing. Any suggestions?

Somebody suggested, it may be easiest to just throw your encryption key and dbconn line (appSettings) into a new web.config (unless you have made other changes in the web.config).

How do I do this and would it work with commander?

If trying the reset password method through the admin, not sql, does the web.config file have to be "touched" before trying to connect with commander