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 2005

Tip: Looking for answers? Try searching our database.

WSE842 error with WSE3

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Mark Bosley - 28 Oct 2005 17:07 GMT
System.ApplicationException: WSE842: The service pipeline could not be
created. ---> System.Configuration.ConfigurationException: The authorization
provider named 'AzMan Authorization Provider' could not be found in
configuration.

I am stumped by the preceding error when I try to run the application from
the article in msdn
http://msdn.microsoft.com/msdnmag/issues/05/11/AzManandWSE30/default.aspx
Combine the Powers of AzMan and WSE 3.0 to Protect Your Web Services

I have gotten the QuickStarts for WSE 3 working fine and I have worked with
AZman before, so I think I have the users, the Azman store etc set up
correctly. And I have WSE 3 authenticating correctly without Azman.

So I am using
   VS 2005 Sept RC1
   WSE 3.0 Oct release
   June Enterprise Library converted for use with VS 2005 with the
Security.Azman and Security.AzMan.Configuration added.
   I am using Azman with an Xml Store. I have users defined on my local
machine and added to Azman groups.
   I switch the demo to UsernameToke over certificate on both the client
and server.
   The build after event has
copy "$(TargetPath)"
"..\..\..\MSDNMag.ServiceAuthorization.SecureInvoiceService\Bin" > nul
   to get it into the web service

HERE IS THE QUESTION
DOES THE securityconfiguration.config need to be in the web service
directory?
If I search for the string 'AzMan Authorization Provider'  (from the error
message) the only place it shows up is in the
wse3policycache.config on the server
     <methodAuthorization authorizationProvider="AzMan Authorization
Provider">
      <action
name="ht://msdn.microsoft.com/msdnmagazine/invoices/ViewInvoices"
tasks="ViewInvoices" />
      <action name="ht//msdn.microsoft.com/msdnmaga....
and in the securityconfiguration.config
<authorizationProvider xsi:type="AzManAuthorizationProviderData"
           name="AzMan Provider"
           storeLocation="msxml://C:/AzManandWSE30/MSDNMagAzStore.xml"
           application="InvoiceApproval"
           scope=""
           auditIdentifierPrefix="AzMan Authorization Provider" />

Any ideas? Thanks

Event Type: Error
Event Source: Microsoft WSE 3.0
Event Category: None
Event ID: 0
Date:  10/28/2005
Time:  10:15:23 AM
User:  N/A
Computer: FOO
Description:
System.ApplicationException: WSE842: The service pipeline could not be
created. ---> System.Configuration.ConfigurationException: The authorization
provider named 'AzMan Authorization Provider' could not be found in
configuration.
  at
Microsoft.Practices.EnterpriseLibrary.Security.SecurityConfigurationView.GetAuthorizationProviderData(String
authorizationProviderName)
  at
Microsoft.Practices.EnterpriseLibrary.Security.AuthorizationProviderFactory.GetConfigurationType(String
authorizationProviderName)
  at
Microsoft.Practices.EnterpriseLibrary.Configuration.ConfigurationFactory.CreateInstance(String
configurationName)
  at
Microsoft.Practices.EnterpriseLibrary.Security.AuthorizationProviderFactory.GetAuthorizationProvider(String
authorizationProviderName)
  at
Microsoft.Practices.EnterpriseLibrary.Security.AuthorizationFactory.GetAuthorizationProvider(String
authorizationProviderName)
  at
MSDNMag.ServiceAuthorization.MethodAuthorizationAssertion.MethodAuthorizationInputFilter..ctor(MethodAuthorizationAssertion
assertion) in
C:\AzManandWSE30\MSDNMag.ServiceAuthorization\MethodAuthorizationAssertion.cs:line
137
  at
MSDNMag.ServiceAuthorization.MethodAuthorizationAssertion.CreateServiceInputFilter(FilterCreationContext
context) in
C:\AzManandWSE30\MSDNMag.ServiceAuthorization\MethodAuthorizationAssertion.cs:line
42
  at
Microsoft.Web.Services3.Design.Policy.CreateServicePipeline(PipelineCreationContext
context)
  at
Microsoft.Web.Services3.PolicyAttribute.Microsoft.Web.Services3.IPipelineProvider.CreateServicePipeline(PipelineCreationContext
context)
  at Microsoft.Web.Services3.Pipeline.TryCreate(Type type, Boolean
forClient)
  at Microsoft.Web.Services3.WseProtocol.CreateProtocolPipeline()
  at Microsoft.Web.Services3.WseProtocol.RouteRequest(SoapServerMessage
message)
  at System.Web.Services.Protocols.SoapServerProtocol.Initialize()
  at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type,
HttpContext context, HttpRequest request, HttpResponse response, Boolean&
abortProcessing)
  --- End of inner exception stack trace ---

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Mark Bosley - 28 Oct 2005 17:36 GMT
Cancel that question. The problem turned out to be that I am an idiot.

Somewhere along the line, I changed the name attribute in the
authorizationProvider element of securityconfiguration.config
<authorizationProvider xsi:type="AzManAuthorizationProviderData" name="AzMan
Authorization Provider" storeLocation="msxml://C:\MSDNMag\Service
Authorization\MSDNMagAzStore.xml" application="InvoiceApproval" scope=""
auditIdentifierPrefix="AzMan Authorization Provider" />

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.