CustomXmlSecurityToken error

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

yaming - 22 Feb 2005 02:31 GMT

hi,
I got an exception "server unavailable , please try later" while
sending the RequestSecurityToken message. What might be causing this ?
I found one notes :
am looking at CustomXmlSecurityToken code samples that came with WSE2RTM.
All worked fine as out of the box
(http://www.dotnetmonster.com/Uwe/ForumPost.aspx?article=dotnet-web-services-enha
ncements:29:O%24XDlM5VEHA.2696%40TK2MSFTNGP09.phx.gbl)
so my question is what is the point of "as out of the box".

appreciate any advice I get

Reply to this Message

kg - 03 Mar 2005 15:27 GMT

Did you find a solution to this issue? I am having the same problem.

> hi,
> I got an exception "server unavailable , please try later" while
[quoted text clipped - 6 lines]
>
> appreciate any advice I get

Reply to this Message

Sidd - 16 Mar 2005 18:47 GMT

Could you please turn on detailedErrors in your web.config on your token
issuer as well as your target service. You could very easily do this by
going to the WSE settings tool (right clicking the project in VS and going
to the WSE 2.0 Settings Tool, clicking the Diagnostics tab and enabling
detailedErrors).

Turning on detailedErrors will give you more information on what is going
wrong. It is quite possible that you haven't either
a) installed the certs correctly (this is highlighted in the docs on how
to install certificates to run samples)
b) given permission to the private key file of the certs to ASP.NET
(this is also highlighted in the docs by using the WseCertificate tool)

Please let me know if you are still having problems

Sidd [MSFT]

> Did you find a solution to this issue? I am having the same problem.
>
[quoted text clipped - 4 lines]
> > am looking at CustomXmlSecurityToken code samples that came with WSE2RTM.
> > All worked fine as out of the box.

(http://www.dotnetmonster.com/Uwe/ForumPost.aspx?article=dotnet-web-services
-enhancements:29:O%24XDlM5VEHA.2696%40TK2MSFTNGP09.phx.gbl)

> > so my question is what is the point of "as out of the box".
> >
> > appreciate any advice I get

Reply to this Message

Version - 20 Mar 2005 12:08 GMT

hi sidd, thanks.
i did as your input,but i am still get that error.
it seems that app can't get the private key for encrypt.

> Could you please turn on detailedErrors in your web.config on your token
> issuer as well as your target service. You could very easily do this by
[quoted text clipped - 22 lines]
> WSE2RTM.
> > > All worked fine as out of the box.

(http://www.dotnetmonster.com/Uwe/ForumPost.aspx?article=dotnet-web-services

> -enhancements:29:O%24XDlM5VEHA.2696%40TK2MSFTNGP09.phx.gbl)
> > > so my question is what is the point of "as out of the box".
> > >
> > > appreciate any advice I get

Reply to this Message

Sidd - 25 Mar 2005 08:09 GMT

Well, in order to encrypt you would need the public key, and not the private
key. Only if you are signing, or you are decrypting you would need the
private key.

Are you sure you have the WSE2QuickStartClient installed in the
CurrentUser->Personal store and the WSE2QuickStartServer installed in the
LocalMachine->Personal store. What permissions are you running your web
service as? If you are running as Network Service, then by switching the
identity of this service to Local System does the problem seem to disappear?
If so, then it is an indication that the private key file has not been given
permissions to be read.

Thanks,

Sidd [MSFT]

> hi sidd, thanks.
> i did as your input,but i am still get that error.
[quoted text clipped - 27 lines]
> > WSE2RTM.
> > > > All worked fine as out of the box.

(http://www.dotnetmonster.com/Uwe/ForumPost.aspx?article=dotnet-web-services

> > -enhancements:29:O%24XDlM5VEHA.2696%40TK2MSFTNGP09.phx.gbl)
> > > > so my question is what is the point of "as out of the box".
> > > >
> > > > appreciate any advice I get

Reply to this Message

Version - 28 Mar 2005 05:10 GMT

sidd,you are so kind,thank you for your help.
now it is running well on my computer.

> Well, in order to encrypt you would need the public key, and not the private
> key. Only if you are signing, or you are decrypting you would need the
[quoted text clipped - 46 lines]
> > > WSE2RTM.
> > > > > All worked fine as out of the box.

(http://www.dotnetmonster.com/Uwe/ForumPost.aspx?article=dotnet-web-services

> > > -enhancements:29:O%24XDlM5VEHA.2696%40TK2MSFTNGP09.phx.gbl)
> > > > > so my question is what is the point of "as out of the box".
> > > > >
> > > > > appreciate any advice I get

Reply to this Message

CustomXmlSecurityToken error

Free Magazines