WSE 2.0: Extending SecurityTokenServiceClient to support SAML Assertions

Ask a Question related to ASP.NET Security, Design and Development.

  1. #1

    Default WSE 2.0: Extending SecurityTokenServiceClient to support SAML Assertions

    In WSE 2.0, using the SecurityTokenServiceClient, I can
    request for a SAML asertion by specifying
    WSTrust.TokenTypes.SAMLAssertion while creating the
    RequestSecurityToken object.

    However, when my SecurityTokenService (a SAML Credentials
    Collector) returns a SAML Assertion,
    RequestSecurityTokenResponse does not recognize the SAML
    assertion and it throws an exception!

    After a bit of digging around, I found that the only
    supported SecurityTokens are UsernameToken, KerberosToken
    and X509SecurityToken. Now, I would like to extend it to
    support a SAML Assertion.

    Is RequestSecurityTokenResponse or
    SecurityTokenServiceClient designed to be extensible? I
    could not find any good virtual functions in these that I
    can override to provide my implementation of a
    SecurityToken.

    Any help is appreciated.

    Thanks
    Hari

    Hari Menon Guest

  2. Similar Questions and Discussions

    1. SAML and .NET?
      I'm doing a scoping study for a Single-Sign-On integration project with a client. The client's SSO interface is built on SAML 1.1 specification...
    2. Signed SAML response in .net
      Hi, I'm trying to verify a signed SAML reponse. It's an enveloped signature with following format: <Response ResponseID="xxx" >...
    3. SAML Module?
      Is there a module that implements the SAML (Security Assertion Markup Language) protocol? If not, is someone already working on one? If so, do...
    4. extending Treenode: how?
      In the documentation it says that the Treenode should not be inherited: why? I want to create a treenode that the checbox has 3 states (off, on,...
    5. Extending CF PoP.
      Is there anyway to extend CFPoP to support additional encoding types? I am getting ' java.io.UnsupportedEncodingException: iso-3979-1. ' Could...
  3. #2

    Default WSE 2.0: Extending SecurityTokenServiceClient to support SAML Assertions

    In WSE 2.0, using the SecurityTokenServiceClient, I can
    request for a SAML asertion by specifying
    WSTrust.TokenTypes.SAMLAssertion while creating the
    RequestSecurityToken object.

    However, when my SecurityTokenService (a SAML Credentials
    Collector) returns a SAML Assertion,
    RequestSecurityTokenResponse does not recognize the SAML
    assertion and it throws an exception!

    After a bit of digging around, I found that the only
    supported SecurityTokens are UsernameToken, KerberosToken
    and X509SecurityToken. Now, I would like to extend it to
    support a SAML Assertion.

    Is RequestSecurityTokenResponse or
    SecurityTokenServiceClient designed to be extensible? I
    could not find any good virtual functions in these that I
    can override to provide my implementation of a
    SecurityToken.

    Any help is appreciated.

    Thanks
    Hari

    Hari Menon Guest

Posting Permissions

  • You may not post new threads
  • You may post replies
  • You may not post attachments
  • You may not edit your posts

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139