The requestXmlServer.ashx is not a physical file; it is a mapping to a custom HttpHandler class. In this particular example, the custom handler is XmlTokenServiceHandler which is a distant descendant of IHttpHandler. If you peek in the web.config under the CustomXmlSecTokenCodeTokenIssuer folder, you will notice an HttpHandler configuration that exposes requestXmlServer.ashx to the world.
The .ashx file extension is configured to be served by IIS when ASP.net is installed. This allows developers to slap the HttpHandler configuration in the web.config without worrying about modifying IIS to map an extension every time a new handler is introduced.
Dave Bettin
Blog: http://www.davebettin.com/me/
nntp://news.microsoft.com/microsoft.public.dotnet.framework.webservices.enhancements/<cff00821.0406161832.50feea3d@posting.google.com>
Hi
I am trying out the CustomXMLSecurityToken sample (installs with the
WSE 2.0 settings tool). In the config file for the
CustomXMLSecTokenCodeClient the appSetting tag contains an entry for
an .ashx file (ASP.NET HTTP Handler). The file that it looks for is
requestXMLServer.ashx file. This is not in the sample. Am I missing
something?
Any help will be appreciated.
Regards
Jag
[microsoft.public.dotnet.framework.webservices.enhancements]
Thanks Dave/ Softwaremaker,
I keep getting an exception "server unavailable , please try later" while
sending the RequestSecurityToken message. What might be causing this ?
Regards
Jag
> The requestXmlServer.ashx is not a physical file; it is a mapping to a custom HttpHandler class. In this particular example, the custom handler is
XmlTokenServiceHandler which is a distant descendant of IHttpHandler. If
you peek in the web.config under the CustomXmlSecTokenCodeTokenIssuer
folder, you will notice an HttpHandler configuration that exposes
requestXmlServer.ashx to the world.
> The .ashx file extension is configured to be served by IIS when ASP.net is installed. This allows developers to slap the HttpHandler configuration
in the web.config without worrying about modifying IIS to map an extension
every time a new handler is introduced.
> Dave Bettin
>
> Blog: http://www.davebettin.com/me/
nntp://news.microsoft.com/microsoft.public.dotnet.framework.webservices.enhancements/<cff00821.0406161832.50feea3d@posting.google.com>
> Hi
>
[quoted text clipped - 10 lines]
>
> [microsoft.public.dotnet.framework.webservices.enhancements]
JosephCooney - 11 Jul 2004 14:40 GMT
I keep getting this error also. I can view the WSDL generated by
XmlTokenServiceHandler (when called via the .ashx http handler) in a
browser, but all requests for tokens fail with a server SOAP fault the
same as Jag (below). Any help would be greatly appreciated.
Joseph Cooney
> Thanks Dave/ Softwaremaker,
>
[quoted text clipped - 36 lines]
> >
> > [microsoft.public.dotnet.framework.webservices.enhancements]
Lucien - 12 Jul 2004 22:45 GMT
Turn detailedErrors on on the service site to debug this (you're now only
seeing a generic error, disable it again after fixing the issue). You can
turn it on through WSE2 add-in in VS.
Make sure you have access to the private key which is a common issue (X509
signing token).
> I keep getting this error also. I can view the WSDL generated by
> XmlTokenServiceHandler (when called via the .ashx http handler) in a
[quoted text clipped - 26 lines]
> > >
> > > Blog: http://www.davebettin.com/me/
nntp://news.microsoft.com/microsoft.public.dotnet.framework.webservices.enhancements/<cff00821.0406161832.50feea3d@posting.google.com>
> > > Hi
> > >
[quoted text clipped - 10 lines]
> > >
> > > [microsoft.public.dotnet.framework.webservices.enhancements]
Jag - 13 Jul 2004 00:48 GMT
Hi Joseph,
The issue that I was having was that :
you need to give access to the ASPNET user so it can read your certificate
store. In practical terms, you need to give your "LocalMachine\ASPNET" user
access to the "{drive}:\Documents and Settings\All Users\Application
Data\Microsoft\Crypto\RSA\MachineKeys" folder (typical read access). After
that, it seems to work fine.
Regards
Jagdeep
> I keep getting this error also. I can view the WSDL generated by
> XmlTokenServiceHandler (when called via the .ashx http handler) in a
[quoted text clipped - 26 lines]
> > >
> > > Blog: http://www.davebettin.com/me/
nntp://news.microsoft.com/microsoft.public.dotnet.framework.webservices.enhancements/<cff00821.0406161832.50feea3d@posting.google.com>
> > > Hi
> > >
[quoted text clipped - 10 lines]
> > >
> > > [microsoft.public.dotnet.framework.webservices.enhancements]
Version - 25 Feb 2005 01:43 GMT
hello Jaq.
I did as what you inputed.but it did not work.
does anybody get any advice ? that will be appreciated.