Invalid Username / Password
I recently upgraded our Gemini to version 2.0.3 and upgraded the screen capture tool as well. I am having a problem though. When I try and submit a screenshot it tells me that my username / password is invalid when I know it is not.
I am also having this problem with the Desktop tool, although I ran the desktop tool with the -dc option from the command line and it said there was a problem with the <security> tag.
I am unsure if these two are related or not, but if anyone knows how to correct either of these problems, it would be greatly appreciated.
Thank you.
gbarnhart
· 1 |
|
Tuesday, March 28, 2006, 7:48:10 PM |
0
|
Please make sure that WSE2.0 SP3 is installed on the web server. |
||||
|
0
|
It is. We just installed it yesterday. |
||||
|
0
|
What is that exact error you are getting when running with the -dc option? |
||||
|
0
|
An error was discovered processing the <Security> header. then I get Login error encountered. Please check username and password. |
||||
|
0
|
Please try and navigate, using a browser, to one of the web services. For example http://localhost/Gemini/webservices/AuthWS.asmx
What do you get?
|
||||
|
0
|
AuthWS The following operations are supported. For a formal definition, please review the Service Description.
|
||||
|
0
|
Please paste your web.config file. Also, paste the settings for the win app. |
||||
|
0
|
<?xml version="1.0" encoding="Windows-1252" ?> "On" Always display custom (friendly) messages |
||||
|
0
|
Here is the App.Config for the Desktop program: <?xml version="1.0" encoding="utf-8" ?>
Here is the Countersoft.Gemini.Desktop.exe.config: <?xml version="1.0" encoding="utf-8"?> |
||||
|
0
|
Here is the GSC.reg for the screen capture: Windows Registry Editor Version 5.00 [HKEYLOCALMACHINE\SOFTWARE\CounterSoft\GeminiScreenCapture] |
||||
|
0
|
All seems ok, did you reboot your server after installing WSE? |
||||
|
0
|
I just rebooted it and still the same problems with both the desktop tool and the screen capture tool... invalid user name and password... |
||||
|
0
|
Did you change the WSE version in the web.config to 2.0.3.0? Try changing it back to 2.0.0.0. |
||||
|
0
|
I changed both instances back to 2.0.0.0 and still no luck. |
||||
|
0
|
|
||||
|
0
|
Alright, I tried pointing it to your site and got a more detailed error: Microsoft.Web.Services2.Security.SecurityFault: An error was discovered processing the <Security> header ---> System.Exception: Creation time in the timestamp can not be in the future. --- End of inner exception stack trace --- at Microsoft.Web.Services2.Security.Utility.Timestamp.CheckValid() at Microsoft.Web.Services2.Security.Utility.Timestamp.LoadXml(XmlElement element) at Microsoft.Web.Services2.Security.Utility.Timestamp..ctor(XmlElement element) at Microsoft.Web.Services2.Security.Security.LoadXml(XmlElement element) at Microsoft.Web.Services2.Security.SecurityInputFilter.ProcessMessage(SoapEnvelope envelope) at Microsoft.Web.Services2.Pipeline.ProcessInputMessage(SoapEnvelope envelope) at Microsoft.Web.Services2.WebServicesExtension.BeforeDeserializeServer(SoapServerMessage message) |
||||
|
0
|
Is this the same error that you are getting when using your own URL? |
||||
|
0
|
No, the error I get when I point it to our gemini server is: An error was discovered processing the <Security> header |
||||
|
0
|
Any ideas? Is there a setting somewhere in any of the setting files or anything I can do to get this to work? I can see there is a problem with a timestamp, but I am unaware of where the error is (ie. Web.config, or any of the other config files). |
||||
|
0
|
Sorry to be a pain, but are you sure you have installed WSE2.0 SP3 and not WSE3.0? |
||||
|
0
|
Yep. Even if I did have WSE3.0 installed on my site, why would I have gotten an error when I pointed it to your site? |
||||
|
0
|
The error that you got when pointed to our site is because you are in a different time zone. |
||||
|
0
|
Try adding <diagnostics> under the <microsoft.web.services2> tag. This will give us extra debug info. Can you also check the time on your server and client? |
||||
|
0
|
I copied and pasted "<diagnostics> and put that under the <microsoft.web.services2> tag and it still gives me the same error: "An error was discovered processing the <security> header." Here is what the <microsoft.web.services2> tag section now looks like: <microsoft.web.services2> <security> Also, the Date/Time on our server is April 5, 2006 4:16 PM and the Date/Time on my local machine is April 5, 2006 4:11 PM |
||||
|
0
|
Can you please try and sychronise your time to be the same as the server? |
||||
|
0
|
well... that seems to be it! will there be any other way around this other than having everyone sync up their time with that server? the way computer clocks speed up and slow down they could be off in an hour or two... |
||||
|
0
|
Thanks for confirming this. Yes, we will improve this soon. |
||||
|
0
|
Thanks for all of the help and troubleshooting with me. I appreciate it. Looking forward to the next releases :) |
||||
|
0
|
You can add some time tolerance (ie not synch the client's and server's time) by amending the web.config file (600 seconds = 10 minutes): <security> <securityTokenManager type="CounterSoft.GeminiBiz.GeminiUsernameTokenManager, CounterSoft.GeminiBiz" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" qname="wsse:UsernameToken" /> <defaultTtlInSeconds>600</defaultTtlInSeconds> <timeToleranceInSeconds>600</timeToleranceInSeconds> </security> <tokenIssuer> <ttlInSeconds>600</ttlInSeconds> </tokenIssuer> |
||||
|