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 / October 2006

Tip: Looking for answers? Try searching our database.

Secure conversation breaks WSE

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
trahan - 01 Sep 2006 23:28 GMT
I was trying to get an increase in performance via the secure
conversation, as per the WSE3 hands on lab.

However, when I turn the establishSecurityContext attribute from false
to true, and reset iis (I'm doing this on both the client and service)
I'm loosing the soap header - "Security requirements are not satisfied
because the security header is not present in the incoming message."

Currently we are using AD to authenticate.  Any ideas on what I might be
missing here?  Please let me know if I can provide any more information
that would be needed to help.

Thanks.
Pablo Cibraro [MVP] - 06 Sep 2006 15:08 GMT
Hi,

Take a look to the WSE trace files or eventlog for more information about
the error. The error message "Security requirements are not satisfied
because the security header is not present in the incoming message" is
something generic and it does not say anything about the real problem.

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

> I was trying to get an increase in performance via the secure
> conversation, as per the WSE3 hands on lab.
[quoted text clipped - 11 lines]
>
> *** Sent via Developersdex http://www.developersdex.com ***
Ben Leach - 12 Oct 2006 14:07 GMT
> I was trying to get an increase in performance via the secure
> conversation, as per the WSE3 hands on lab.
[quoted text clipped - 11 lines]
>
> *** Sent via Developersdex http://www.developersdex.com ***

I have noticed a similar problem to this.  It seems that if you use a Custom UsernameTokenManager and try to use SecureConversation you get that error.

As soon as I took out the custom UsernameTokenManager the problem went away.

Of course, this worked perfectly on my local machine running IIS 5 but when I moved the web service to the 2003 Server machine I started seeing this problem.

I have made sure that the users have access to the certificates.

If anyone finds a solution then it would be greatly appreciated if they would e-mail me with their solution

Ben Leach

Posted from http://www.topxml.com/renntp using reNNTP: the website based NNTP reader.

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.