CodeVerge.Net Beta


   Explore    Item Entry    Members      Register  Login  
NEWSGROUP
.NET
Algorithms-Data Structures
Asp.Net
C Plus Plus
CSharp
Database
HTML
Javascript
Linq
Other
Regular Expressions
VB.Net
XML

Free Download:
Zone: > NEWSGROUP > Asp.Net Forum > general_asp.net.security Tags:
Item Type: NewsGroup Date Entered: 7/9/2007 5:26:58 PM Date Modified: Subscribers: 0 Subscribe Alert
Rate It:
(NR, 0)
XPoints: N/A Replies: 2 Views: 168 Favorited: 0 Favorite
Can Reply:  No Members Can Edit: No Online: Yes
3 Items, 1 Pages 1 |< << Go >> >|
asr0502
Asp.Net User
WSE 3.0 security issue7/9/2007 5:26:58 PM

0/0

I'm having an issue implementing an encryption policy in WSE 3.0 (right now I'm just testing using x.509 certificates that I generated using makecert).  I'm doing this on a windows xp development box running IIS 5.0.  I keep getting a security exception, and I'm not quite sure why.  I'm pretty new to WSE in general, so any direction that you all can provide is very much appreciated.  The exception being thrown is...

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

 Here is a soap message from the output trace...

<?xml version="1.0" encoding="utf-8"?>
<log>
  <outputMessage utc="7/9/2007 5:23:44 PM" messageId="urn:uuid:ca65d99e-0a6c-4c3d-af2b-6e2924063e44">
    <processingStep description="Unprocessed message">
      <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
        <soap:Body>
          <wst:RequestSecurityToken xmlns:wst="http://schemas.xmlsoap.org/ws/2005/02/trust">
            <wst:TokenType>http://schemas.xmlsoap.org/ws/2005/02/sc/sct</wst:TokenType>
            <wst:RequestType>http://schemas.xmlsoap.org/ws/2005/02/trust/Issue</wst:RequestType>
            <wst:Entropy>
              <wst:BinarySecret Type="http://schemas.xmlsoap.org/ws/2005/02/trust/SymmetricKey">UOcqd3TrLShb+gxpscjR2w==</wst:BinarySecret>
            </wst:Entropy>
            <wst:Lifetime>
              <wsu:Expires xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">2007-07-09T21:23:44Z</wsu:Expires>
            </wst:Lifetime>
          </wst:RequestSecurityToken>
        </soap:Body>
      </soap:Envelope>
    </processingStep>
    <processingStep description="Entering SOAP filter Microsoft.Web.Services3.Design.MutualCertificate11Assertion+ClientOutputFilter" />
    <processingStep description="Exited SOAP filter Microsoft.Web.Services3.Design.MutualCertificate11Assertion+ClientOutputFilter" />
    <processingStep description="Processed message">
      <soap:Envelope xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
        <soap:Header>
          <wsa:Action wsu:Id="Id-1a5d50b1-1b38-4d3d-b80c-7b196e002ac2">http://schemas.xmlsoap.org/ws/2005/02/trust/RST/SCT</wsa:Action>
          <wsa:MessageID wsu:Id="Id-0dcef0ac-6c91-4992-b0af-73c0dc817043">urn:uuid:ca65d99e-0a6c-4c3d-af2b-6e2924063e44</wsa:MessageID>
          <wsa:ReplyTo wsu:Id="Id-27649cfd-3ad8-4674-906a-935f1fa37e82">
            <wsa:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:Address>
          </wsa:ReplyTo>
          <wsa:To wsu:Id="Id-f7ada615-e74e-471e-ae71-0d7d69a46add">http://localhost:8080/LuceneDemo/Consentra.asmx</wsa:To>
          <wsse:Security soap:mustUnderstand="1">
            <wsu:Timestamp wsu:Id="Timestamp-443cea73-b722-4f26-ad26-1c19d2ef0834">
              <wsu:Created>2007-07-09T17:23:44Z</wsu:Created>
              <wsu:Expires>2007-07-09T17:28:44Z</wsu:Expires>
            </wsu:Timestamp>
            <wsse:BinarySecurityToken ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3" EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="SecurityToken-78ce56ff-fa5d-49ee-9403-e1f4010264c1">MIIB9jCCAV+gAwIBAgIQ2qIevlCzTa5PNCq2kpT2bjANBgkqhkiG9w0BAQQFADAUMRIwEAYDVQQDEwlCb3Vya2VLZXkwHhcNMDcwNzA2MjM0NDEyWhcNMzkxMjMxMjM1OTU5WjAUMRIwEAYDVQQDEwlCb3Vya2VLZXkwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAPFfnxK9RTwfbugY/lDmRAKFMxvIj4u1xLvGXBw8jlnWP4mGyYo/Q5H7p8J8nHmqa1C8Guhb+Pixlj+Q5DayWRLFRK9pQ+R8aLw8yYL1XVe9W4F541+7kT1HTXfSXn2JgqyhIH+LAtAZ+hh/927doxOReA5TjzYBIU9mFotOuDEzAgMBAAGjSTBHMEUGA1UdAQQ+MDyAEDkfggLuJXeQm/afzta8yzihFjAUMRIwEAYDVQQDEwlCb3Vya2VLZXmCENqiHr5Qs02uTzQqtpKU9m4wDQYJKoZIhvcNAQEEBQADgYEANoVzGNGBAHFUjyY0IsVEeYeaXEZDy842ihtOVzhnFllo0BxHXGG3OBE7MuMx7hAwQJdYXymeYMEPvghoXRyalVC83ceqyDyYy34YftjCoWH3gmX0W4Vo6d1B/nbwUo0M4GNDW1CvM1evympnunqDpQE78Y7pW3+esn1vICCPRd0=</wsse:BinarySecurityToken>
            <xenc:EncryptedKey Id="SecurityToken-9d6c0b42-f1c4-49a3-b37f-708b6edb4d26" xmlns:xenc="http://www.w3.org/2001/04/xmlenc#">
              <xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p">
                <ds:DigestMethod xmlns:ds="http://www.w3.org/2000/09/xmldsig#" Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
              </xenc:EncryptionMethod>
              <KeyInfo xmlns="http://www.w3.org/2000/09/xmldsig#">
                <wsse:SecurityTokenReference>
                  <wsse:KeyIdentifier ValueType="http://docs.oasis-open.org/wss/oasis-wss-soap-message-security-1.1#ThumbprintSHA1" EncodingType="t/XRFBXinUOz/6CBkiGVxw3L60s=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary">t/XRFBXinUOz/6CBkiGVxw3L60s=</wsse:KeyIdentifier>
                </wsse:SecurityTokenReference>
              </KeyInfo>
              <xenc:CipherData>
                <xenc:CipherValue>3CxN5FKysnTkWmXzPF1xvB3N8U1HJ6kCv5LCXX4znVdTuH1d9xeZsnZdLooqfuhpC0gSVaw30+UxRaWBZpIFKqUIdp4HcEdMBNn1PUxl6Dl8vYC/HIENtG6cEg6ZSF+C1USduhWLCrhiQqSSENmNaKzHkwulYu1QQyswwT8wIe8=</xenc:CipherValue>
              </xenc:CipherData>
            </xenc:EncryptedKey>
            <wssc:DerivedKeyToken wsu:Id="SecurityToken-91e1b0a1-0555-4f08-bde0-5344eac42b44" Algorithm="http://schemas.xmlsoap.org/ws/2005/02/sc/dk/p_sha1" xmlns:wssc="http://schemas.xmlsoap.org/ws/2005/02/sc">
              <wsse:SecurityTokenReference>
                <wsse:Reference URI="#SecurityToken-9d6c0b42-f1c4-49a3-b37f-708b6edb4d26" ValueType="http://docs.oasis-open.org/wss/oasis-wss-soap-message-security-1.1#EncryptedKey" />
              </wsse:SecurityTokenReference>
              <wssc:Generation>0</wssc:Generation>
              <wssc:Length>24</wssc:Length>
              <wssc:Label>WS-SecureConversationWS-SecureConversation</wssc:Label>
              <wssc:Nonce>ALj7o/TDWslV5TitGgb9fQ==</wssc:Nonce>
            </wssc:DerivedKeyToken>
            <wssc:DerivedKeyToken wsu:Id="SecurityToken-bb003e6a-27b3-4649-8213-eaef37447afa" Algorithm="http://schemas.xmlsoap.org/ws/2005/02/sc/dk/p_sha1" xmlns:wssc="http://schemas.xmlsoap.org/ws/2005/02/sc">
              <wsse:SecurityTokenReference>
                <wsse:Reference URI="#SecurityToken-9d6c0b42-f1c4-49a3-b37f-708b6edb4d26" ValueType="http://docs.oasis-open.org/wss/oasis-wss-soap-message-security-1.1#EncryptedKey" />
              </wsse:SecurityTokenReference>
              <wssc:Generation>0</wssc:Generation>
              <wssc:Length>32</wssc:Length>
              <wssc:Label>WS-SecureConversationWS-SecureConversation</wssc:Label>
              <wssc:Nonce>iPuzb2B+kyw6vJDudxCs1A==</wssc:Nonce>
            </wssc:DerivedKeyToken>
            <xenc:ReferenceList xmlns:xenc="http://www.w3.org/2001/04/xmlenc#">
              <xenc:DataReference URI="#Enc-a686d7bc-0b65-48f4-981e-96e56806c6bd" />
            </xenc:ReferenceList>
            <Signature Id="Sig-a8ed3380-77ed-4595-9345-389ba5e07ff7" xmlns="http://www.w3.org/2000/09/xmldsig#">
              <SignedInfo>
                <ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" />
                <SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#hmac-sha1" />
                <Reference URI="#Id-1a5d50b1-1b38-4d3d-b80c-7b196e002ac2">
                  <Transforms>
                    <Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
                  </Transforms>
                  <DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
                  <DigestValue>rIJLlWZbJRVkVGBHe31nUCzRFI8=</DigestValue>
                </Reference>
                <Reference URI="#Id-0dcef0ac-6c91-4992-b0af-73c0dc817043">
                  <Transforms>
                    <Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
                  </Transforms>
                  <DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
                  <DigestValue>XJzy2lBnaguH+u5a09RI3AyRJjs=</DigestValue>
                </Reference>
                <Reference URI="#Id-27649cfd-3ad8-4674-906a-935f1fa37e82">
                  <Transforms>
                    <Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
                  </Transforms>
                  <DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
                  <DigestValue>8IQcfR2HhyDEQh7Vdhj+yw+h1+A=</DigestValue>
                </Reference>
                <Reference URI="#Id-f7ada615-e74e-471e-ae71-0d7d69a46add">
                  <Transforms>
                    <Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
                  </Transforms>
                  <DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
                  <DigestValue>L+lPpoZ0YS6oRqqpd7XY104drIA=</DigestValue>
                </Reference>
                <Reference URI="#Timestamp-443cea73-b722-4f26-ad26-1c19d2ef0834">
                  <Transforms>
                    <Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
                  </Transforms>
                  <DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
                  <DigestValue>GGkEhti37qlYcrP57tnLMpwYot0=</DigestValue>
                </Reference>
                <Reference URI="#Id-b20883c4-d80e-499b-9dae-84eb74ca4e1b">
                  <Transforms>
                    <Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
                  </Transforms>
                  <DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
                  <DigestValue>KF0nMCnDq3DTWJvW2T2g95QetW8=</DigestValue>
                </Reference>
              </SignedInfo>
              <SignatureValue>l+SWg11tdphxJX1rlbDMBgLYs44=</SignatureValue>
              <KeyInfo>
                <wsse:SecurityTokenReference>
                  <wsse:Reference URI="#SecurityToken-91e1b0a1-0555-4f08-bde0-5344eac42b44" ValueType="http://schemas.xmlsoap.org/ws/2005/02/sc/dk" />
                </wsse:SecurityTokenReference>
              </KeyInfo>
            </Signature>
            <Signature xmlns="http://www.w3.org/2000/09/xmldsig#">
              <SignedInfo>
                <ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" />
                <SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1" />
                <Reference URI="#Sig-a8ed3380-77ed-4595-9345-389ba5e07ff7">
                  <Transforms>
                    <Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
                  </Transforms>
                  <DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
                  <DigestValue>VQ9A9BCQNX7rjNWOlju/JmCreJw=</DigestValue>
                </Reference>
              </SignedInfo>
              <SignatureValue>aod2ZK0pHY89tswJcxHqI6vpIFnFv1jRIykQluc7ZCfsIIsPoyK7n3q43uZmAhqNhsk7uW3Lnlyt5uPA0dD9rgRj3SHNpByhnRZW4ssvyx7p3o0wn1H2ufcPMANTWOt4VHtvBlomTxxB8VGnUb93G43OTR3cNR8DxteotRMfAv0=</SignatureValue>
              <KeyInfo>
                <wsse:SecurityTokenReference>
                  <wsse:Reference URI="#SecurityToken-78ce56ff-fa5d-49ee-9403-e1f4010264c1" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3" />
                </wsse:SecurityTokenReference>
              </KeyInfo>
            </Signature>
          </wsse:Security>
        </soap:Header>
        <soap:Body wsu:Id="Id-b20883c4-d80e-499b-9dae-84eb74ca4e1b">
          <xenc:EncryptedData Id="Enc-a686d7bc-0b65-48f4-981e-96e56806c6bd" Type="http://www.w3.org/2001/04/xmlenc#Content" xmlns:xenc="http://www.w3.org/2001/04/xmlenc#">
            <xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#aes256-cbc" />
            <KeyInfo xmlns="http://www.w3.org/2000/09/xmldsig#">
              <wsse:SecurityTokenReference>
                <wsse:Reference URI="#SecurityToken-bb003e6a-27b3-4649-8213-eaef37447afa" ValueType="http://schemas.xmlsoap.org/ws/2005/02/sc/dk" />
              </wsse:SecurityTokenReference>
            </KeyInfo>
            <xenc:CipherData>
              <xenc:CipherValue>qF1rL/TyJtaVM3apU+pvZG7Re9oRWBTLvOV9HThBIjiQdgG6T3UiHZQ0hMpM5OSK76AB4YodmJ/kUfLU0C+atP5RcXeycVfhKOGOFP1sG7TAaYDVAdqzU4Lq3rQIboJs1yDQPVZfRqCWnb9QyCItvrFtFt/RMflDvwFSXLAlKlIqcXEsiFv5/1G3hC5BZFUzxQgUPBsu3+NtaXpWkXTi+lqXI6kfma4VBJjgYi5Vf9r6I4XHYCieBaNybcm60knSZvMpo9tha5jYQio+EVeJ6/j0O5eRKRQX5+iOT2SXH1v4s/wWWivjqzppk3wKXB2gaOGbEasKVjswvtWc68D4MhoKOcK0MbSc29PjQvB6ZFrwHhNvOOVhNipqYiS5WXkB5hNBLBm3XOmzdCU1GzKH+fFFxiaPv3a2gFhve0FWdTEcucP+9J3sZbhrZtlfywDjrOpRHC7y5q7np4KMrt038hAFHWxsrEa4rQ66IvOT13VPhRnmGGgkAndUfqwI/jOmPcRRGkqtOkSpJjnpyGXk6vkx1Tz07zcl7hRjPciuGpAEGhmpLvwOlaqyInRFR0ftaNA7v0RLST6oR3Oi8boIJPVJ/FQgaRDnJp2ymtd/H51uz36vMKIzCtVYx2cA1oTYqc+M9a8HbferCgO5hmez8bKgNu3i6Qvj8qOzSoTbt3Xo2e5Ui6u+7DUt6EX3pQrr2EReI7BXDiuVpmfSPGYxTHp9KA5ppMpXEQjBuOIX8j17bu5YdAkPmjRFFVQApQFhBUirAGjbUXjOBe8ypISaOWBuNdY2g3YY0ks7r8ZPoMA=</xenc:CipherValue>
            </xenc:CipherData>
          </xenc:EncryptedData>
        </soap:Body>
      </soap:Envelope>
    </processingStep>
  </outputMessage>
  <outputMessage utc="7/9/2007 5:23:45 PM" messageId="urn:uuid:7cc4dc0f-832c-4fe3-b720-684908a7375f">
    <processingStep description="Unprocessed message">
      <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
        <soap:Body>
          <GetSearchResults xmlns="http://www.consentra.com/w3svc">
            <token>
              <stringHash>1271631999214623994214230688966137203820914784224160194692281372392310854209161751785125523792233181692156742185913713841382052549038126202555719162108122130394213</stringHash>
            </token>
            <searchInfo>
              <ContainerName>/Bourke Consulting/News</ContainerName>
              <specificObj>0</specificObj>
              <breakOut>true</breakOut>
              <AllAttributes>false</AllAttributes>
              <requestedAttributes>
                <string>Headline</string>
                <string>Release Date</string>
              </requestedAttributes>
            </searchInfo>
          </GetSearchResults>
        </soap:Body>
      </soap:Envelope>
    </processingStep>
    <processingStep description="Entering SOAP filter Microsoft.Web.Services3.Design.MutualCertificate11Assertion+ClientOutputFilter" />
    <processingStep description="Exception thrown: WSE910: An error happened during the processing of a response message, and you can find the error in the inner exception.  You can also find the response message in the Response property.">   at Microsoft.Web.Services3.Messaging.SoapClient.SendRequestResponse(String methodname, SoapEnvelope envelope)
   at Microsoft.Web.Services3.Security.SecurityTokenServiceClient.RequestSecurityToken(SecurityTokenMessage request, String methodName)
   at Microsoft.Web.Services3.Security.SecurityContextTokenServiceClient.RequestSecurityContextToken(AppliesTo appliesTo)
   at Microsoft.Web.Services3.Security.SecurityContextTokenServiceClient.IssueSecurityContextToken(AppliesTo appliesTo)
   at Microsoft.Web.Services3.Security.Tokens.SecurityContextTokenManager.RequestTokenFromIssuer(EndpointReference tokenIssuer, String tokenType, AppliesTo appliesTo, Policy policy, SoapProtocolVersion soapVersion, StateManager messageState, StateManager operationState, StateManager sessionState)
   at Microsoft.Web.Services3.Security.SecureConversationClientSendSecurityFilter.EstablishSecureConversation(SoapEnvelope envelope)
   at Microsoft.Web.Services3.Security.SecureConversationClientSendSecurityFilter.SecureMessage(SoapEnvelope envelope, Security security)
   at Microsoft.Web.Services3.Security.SendSecurityFilter.ProcessMessage(SoapEnvelope envelope)
   at Microsoft.Web.Services3.Pipeline.ProcessOutputMessage(SoapEnvelope envelope)</processingStep>
  </outputMessage>
</log>

 

And the input trace:

 

<?xml version="1.0" encoding="utf-8"?>
<log>
  <inputMessage utc="7/9/2007 5:23:45 PM" messageId="urn:uuid:d2c54635-3b10-4601-8690-a9c3fe3c28b0">
    <processingStep description="Unprocessed message">
      <soap:Envelope xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
        <soap:Header>
          <wsa:Action>http://schemas.xmlsoap.org/ws/2004/08/addressing/fault</wsa:Action>
          <wsa:MessageID>urn:uuid:d2c54635-3b10-4601-8690-a9c3fe3c28b0</wsa:MessageID>
          <wsa:RelatesTo>urn:uuid:ca65d99e-0a6c-4c3d-af2b-6e2924063e44</wsa:RelatesTo>
          <wsa:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To>
        </soap:Header>
        <soap:Body>
          <soap:Fault>
            <faultcode>soap:Server</faultcode>
            <faultstring>System.Web.Services.Protocols.SoapHeaderException: Server unavailable, please try later ---&gt; System.ApplicationException: WSE841: An error occured processing an outgoing fault response. ---&gt; System.Web.Services.Protocols.SoapHeaderException: Microsoft.Web.Services3.Security.SecurityFault: The security token could not be authenticated or authorized ---&gt; System.Security.SecurityException: WSE3003: The certificate's trust chain could not be verified.  Please check if the certificate has been properly installed in the Trusted People Certificate store.  Or you might want to set allowTestRoot configuration section to true if this is a test certificate.
   at Microsoft.Web.Services3.Security.Tokens.X509SecurityToken.VerifyChain(X509Chain chain)
   at Microsoft.Web.Services3.Security.Tokens.X509SecurityToken.VerifyTrust()
   at Microsoft.Web.Services3.Security.Tokens.X509SecurityToken.Verify()
   at Microsoft.Web.Services3.Security.Tokens.X509SecurityTokenManager.VerifyToken(SecurityToken token)
   at Microsoft.Web.Services3.Security.Tokens.SecurityTokenManager.LoadBinarySecurityToken(XmlElement element)
The Zone of the assembly that failed was:
MyComputer
   --- End of inner exception stack trace ---
   at Microsoft.Web.Services3.Security.Tokens.SecurityTokenManager.LoadBinarySecurityToken(XmlElement element)
   at Microsoft.Web.Services3.Security.Tokens.SecurityTokenManager.GetTokenFromXml(XmlElement element)
   at Microsoft.Web.Services3.Security.Security.LoadToken(XmlElement element, SecurityConfiguration configuration, Int32&amp; tokenCount)
   at Microsoft.Web.Services3.Security.Security.LoadXml(XmlElement element)
   at Microsoft.Web.Services3.Security.Security.CreateFrom(SoapEnvelope envelope, String localActor, String serviceActor)
   at Microsoft.Web.Services3.Security.ReceiveSecurityFilter.ProcessMessage(SoapEnvelope envelope)
   at Microsoft.Web.Services3.Pipeline.ProcessInputMessage(SoapEnvelope envelope)
   at Microsoft.Web.Services3.WseProtocol.FilterRequest(SoapEnvelope requestEnvelope)
   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&amp; abortProcessing)
   --- End of inner exception stack trace ---
   --- End of inner exception stack trace ---</faultstring>
            <faultactor>http://localhost:8080/LuceneDemo/Consentra.asmx</faultactor>
          </soap:Fault>
        </soap:Body>
      </soap:Envelope>
    </processingStep>
    <processingStep description="Entering SOAP filter Microsoft.Web.Services3.Design.MutualCertificate11Assertion+ClientInputFilter" />
    <processingStep description="Exception thrown: Security requirements are not satisfied because the security header is not present in the incoming message.">   at Microsoft.Web.Services3.Security.SecureConversationClientReceiveSecurityFilter.ValidateMessageSecurity(SoapEnvelope envelope, Security security)
   at Microsoft.Web.Services3.Security.ReceiveSecurityFilter.ProcessMessage(SoapEnvelope envelope)
   at Microsoft.Web.Services3.Pipeline.ProcessInputMessage(SoapEnvelope envelope)</processingStep>
  </inputMessage>
</log>

 

Any help you can provide is appreciated.
asr0502
Asp.Net User
Re: WSE 3.0 security issue7/9/2007 10:09:10 PM

0/0

I figured this out.  The issue was that the certificate generated by makecert wasn't trusted.  Since this is only a test certificate, I authorized it and was eventually able to get it working.  The end! 

binypanackal
Asp.Net User
Re: WSE 3.0 security issue7/18/2007 12:51:44 PM

0/0

me also having the same problem could you please help to sort out this problem 
3 Items, 1 Pages 1 |< << Go >> >|


Free Download:

Books:
Pro Scalable .NET 2.0 Application Designs Authors: Joachim Rossberg, Rickard Redler, Pages: 507, Published: 2005
Expert Service-Oriented Architecture in C# 2005 Authors: Jeffrey Hasan, Mauricio Duran, Pages: 246, Published: 2006
Pro WCF: Practical Microsoft SOA Implementation Authors: Chris Peiris, Dennis Mulder, Shawn Cicoria, Amit Bahree, Nishith Pathak, Pages: 475, Published: 2007
The Complete Reference to Professional Soa With Visual Studio 2005 (C# & Vb 2005) .net 3.0 Authors: Tom Gao, Pages: 700, Published: 2007
Professional XML Authors: Bill Evjen, Kent Sharkey, Thiru Thangarathinam, Michael Kay, Alessandro Vernet, Sam Ferguson, Pages: 856, Published: 2007
Professional Web 2.0 Programming Authors: Eric Van der Vlist, Danny Ayers, Erik Bruchez, Joe Fawcett, Alessandro Vernet, Pages: 522, Published: 2006
.NET Security and Cryptography Authors: Peter Thorsteinson, G. Gnana Arun Ganesh, Arun Ganesh, Pages: 466, Published: 2003
Expert ASP.NET 2.0 Advanced Application Design: Advanced Application Design Authors: Dominic Selly, Andrew Troelsen, Tom Barnaby, Pages: 459, Published: 2005
Java EE and .net Interoperability: Integration Strategies, Patterns, and Best Practices Authors: Marina Fisher, Ray Lai, Sonu Sharma, Laurence Moroney, Pages: 608, Published: 2006
Professional WCF Programming: .NET Development with the Windows Communication Foundation Authors: Scott Klein, Pages: 430, Published: 2007

Web:
Security Briefs: Security Features in WSE 3.0 Contents. Here Comes WSE 3.0 Turnkey Security Assertions ..... article on WSE and Authorization Manager in this issue, as well as Mark Fussell's WSE 3.0 ...
WSE 3.0 security issue - ng.asp-net-forum.security - fix error ... WSE 3.0 security issue, > ROOT > NEWSGROUP > Asp.Net Forum > general_asp.net. security, Date: 7/9/2007 5:26:58 PM, Replies: 2, Views: 29, Subscribers: 0, ...
In the Trenches : WSE 3.0 How to Setup Mutual Authentication May 25, 2007 ... NET 2.0 and WSE 3.0 installed as well as VS.NET 2005. .... error is that it can’ t read the private key because of access security issues. ...
Welcome to Web Services Enhancements (WSE) 3.0 - hq_space - Live ... Jun 25, 2008 ... The Policy Advisor is a security tool for WSE 3.0. ... provide strong security guarantees; nonetheless, Policy Advisor can find issues that ...
Service Station: All About ASMX 2.0, WSE 3.0, and WCF WSE 3.0 only supports the security framework while WCF supports the .... were written for WSE 2.0, but they port over to WSE 3.0 without many issues. ...
The Hogg Blog : SAML STS for WSE 3.0 (reposted) re: SAML STS for WSE 3.0 (reposted). Almost all errors that people received are due to security permissions on the private keys associated with certificates ...
Interoperability between WCF and WSE 3.0 - Lazy Developer To create this example an anonymous web service was used so all security ... When we know the issues about WS-addressing supported by WSE 3.0 and WCF ...
Re: WSE 3.0 UsernameOverTransport Problem working on integrating WSE 3.0 into an web service. The web service is ... web service will be vulnerable, so to improve security use the WSE.. ... just ...
WSE 3.0 Security? - .NET Web Services WSE 3.0 Security?. Get answers to your questions in our .NET Web Services forum.
CodeProject: WebService Authentication with UsernameToken in WSE ... Under the Security tab, in the Security Tokens Managers area, click Add. ..... I 'm having the same issue. WSE 3.0 framework doesn't call my ...




Search This Site:










how do i configure an ssl connection in vb

how to get this html address http://www.domain.com/temp/book__3j1v4k4lj7lh3e3p4l6li5h__.htm

onmenuitemclick causing postback all the time

strange error found in searchdatastore

web services recomendation?

string/number manip.

horizontal scrollbar in listbox

createuser wizard helpppp!!!

passing variables, please please help :)

need help in deploying asp.net web app to file share

how to build my createuser() method to put some paramters like sex in the membershipprovider?

correct display of webcontrols(multipage) using non microsoft browser

control must be in server form

master page custom event problem

bug: urls not resolving correctly

asp.net membership failure

host is offering to install dotnetnuke if i do the homework...

does tabstrip works on beta2?

some question follow the building a custom database-driven site map provider

node duplication in treeview

dnn modules communication

eventvalidation in .net 2.0

email for sub-portal

do i need to exit a thread?

webpart samples on asp.net quickstart tutorials dont work

localization & global javascript

i downloaded asp.net so i could design a battle.net bot

error message when trying to view .aspx file

browser problem

trying to run fop.bat with some cmd line args - does nothing.
 
All Times Are GMT