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

Tip: Looking for answers? Try searching our database.

Error: Security requirements are not satisfied because...

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
RK - 12 Jan 2006 14:52 GMT
Hi,
  I am using Usernametoken authentication with WSE 3.0 to check the user
credentials against the database, but I am getting the following error message

Security requirements are not satisfied because the security header is not
present in the incoming message

actually I didn't implement the validation of the password, I am just
returning the password inside the authenticationtoken class like this.
   protected override string AuthenticateToken(UsernameToken token)
   {
       return token.Password;
   }

I added security token manager to the webservice and added a policy. while
adding policy, I left authorization unchecked and checked the box for
security extensions and unchecked the establish security session and selected
the certificate WSE2QuickStartServer and clicked finish finally. did the same
for client.
   since I am not using the default windows authentication this time, it
should not check the user id and password against windows store. but I don't
know why I am getting this message.

can anybody help me please?

regards,
RK.
Julie Lerman - 14 Jan 2006 21:17 GMT
It sounds to me like you set a policy on the service but not on the client
and that the service is complaining that it is not being sent a security
token.

Do you have a client policy? Is it being set in code in your client app?
(myProxy.SetPolicy("myclientpolicy")

Are you creating a usernameToken on the client side and attaching that to
the proxy? (myProxy.SetClientCredential(myUserNameToken).?

> Hi,
>   I am using Usernametoken authentication with WSE 3.0 to check the user
[quoted text clipped - 27 lines]
> regards,
> RK.

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.