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 / November 2005

Tip: Looking for answers? Try searching our database.

Gotcha with UsernameTokenManger migration to WSE 3

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Mark Arnott - 29 Nov 2005 21:44 GMT
I migrated a custom UsernameTokenManager class from .Net 1.1/WSE 2 to
.Net2.0/WSE 3 and ran into an annoying problem.

The WSE 2.0 config that worked was:

<security>
 <securityTokenManager
     type="Proxies.MyUsernameTokenManager, IfisClient"
     
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
     qname="wsse:UsernameToken" />
</security>

The migration wizard gave me the following:

<security>
 <securityTokenManager>
  <add
     localName="wsse:UsernameToken"
     type="Proxies.MyUsernameTokenManager, IfisClient"
     
namespace="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"/>
 </securityTokenManager>
</security>

This did not work because the migration wizard did not remove the wsse:
prefix.  Xml namespaces strike again!

But I spent way too long trying to figure that out.  

I hope this tidbit of knowledge was useful
Pablo Cibraro - 30 Nov 2005 13:25 GMT
Hi Mark,
The configuration for the username token manager should look like this:

<securityTokenManager>
       <add type="Proxies.MyUsernameTokenManager, IfisClient"
namespace="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
localName="UsernameToken"/>
</securityTokenManager>

Regards,
Pablo Cibraro
http://weblogs.asp.net/cibrax
http://www.lagash.com

>I migrated a custom UsernameTokenManager class from .Net 1.1/WSE 2 to
> .Net2.0/WSE 3 and ran into an annoying problem.
[quoted text clipped - 27 lines]
>
> I hope this tidbit of knowledge was useful
Mark Arnott - 30 Nov 2005 14:25 GMT
Yes Pablo that is correct.

It just seems odd to me that we have to declare an attribute named
'namespace' that looks a lot like an xml namespace but actually isn't.  Why
couldn't WSE 3 just declare an actual xml namspace like WSE 2 did?

> Hi Mark,
> The configuration for the username token manager should look like this:
[quoted text clipped - 4 lines]
> localName="UsernameToken"/>
> </securityTokenManager>

Rate this thread:







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.