Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / Web Services / August 2004

Tip: Looking for answers? Try searching our database.

Cannot Start Custom Token Manager

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Chris Jones - 29 Jul 2004 22:31 GMT
  Following several online examples, we have implemented the following  using WSE 2.0:

In the Web Servic .asmx file:
namespace WebService1

{
    public class Service1 : System.Web.Services.WebService
    {
          public class AuthenticationManager : UsernameTokenManager
        {
            protected override string AuthenticateToken(UsernameToken token)
            {
                return token.Password;;
            }
        }
...

  And in the Service's Web.config file we have the following:
<security>
    <securityTokenManager
        qname="wsse:UsernameToken"
        xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/12/secext"
        type="WebService1.AuthenticationManager, WebService1" />

  When we run the client application, we get an exception when it calls the web service:

System.Web.Services.Protocols.SoapHeaderException: Server unavailable, please try later ---> System.Configuration.ConfigurationException: WSE032: There was an error loading the microsoft.web.services2 configuration section. ---> System.Configuration.ConfigurationException: WSE040: Type WebService1.AuthenticationManager, WebService1 could not be loaded. Please check the configuration file. at System.Web.Configuration.HttpConfigurationRecord.Evaluate(String configKey, SectionRecord section)

  Any clues as to what we're doing wrong?

  Thanks,
  Chris
Jeffrey Hasan - 03 Aug 2004 08:42 GMT
I don't know if this will solve the entire issue, but the namespace looks
wrong. It should be:

xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecuri
ty-secext-1.0.xsd" qname="wsse:UsernameToken"

If you are using the production build of WSE 2.0 then it uses the OASIS
standard for WS-Security.

Jeffrey Hasan, MCSD
President, Bluestone Partners, Inc.
-----------------------------------------------
Author of: Expert SOA in C# Using WSE 2.0 (APress, 2004)
http://www.bluestonepartners.com/soa.aspx

>    Following several online examples, we have implemented the following  using WSE 2.0:
>
[quoted text clipped - 23 lines]
>
> System.Web.Services.Protocols.SoapHeaderException: Server unavailable, please try later ---> System.Configuration.ConfigurationException: WSE032:
There was an error loading the microsoft.web.services2 configuration
section. ---> System.Configuration.ConfigurationException: WSE040: Type
WebService1.AuthenticationManager, WebService1 could not be loaded. Please
check the configuration file. at
System.Web.Configuration.HttpConfigurationRecord.Evaluate(String configKey,
SectionRecord section)

>    Any clues as to what we're doing wrong?
>
>    Thanks,
>    Chris

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.