wsit
  1. wsit
  2. WSIT-84

Multiple endpoint access in different WAR's leads to signature verification

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Blocker Blocker
    • Resolution: Won't Fix
    • Affects Version/s: current
    • Fix Version/s: 1.0
    • Component/s: security
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: Sun

    • Issuezilla Id:
      84

      Description

      This issue is similar to https://wsit.dev.java.net/issues/show_bug.cgi?id=81

      In this case I have two different WAR's deployed in Glassfish. One uses
      SecurityPolicy Dsig (XWSS) and other uses SecurityPolicy Dsig + MTOM (XWSS).

      When I access each individually - all works. When I access them one after the
      other, only the first one works. Second one throws signatureverification errors.

      I turned on signature logging and the two server.log files are attached. In the
      file named mtom1, the endpoint with mtom is accessed first. In the file named
      mtom2 the endpoint with mtom is accessed second.

        Activity

        Hide
        sameer_t added a comment -

        Created an attachment (id=48)
        output when WSIT jars are not in war but loaded from Glassfish

        Show
        sameer_t added a comment - Created an attachment (id=48) output when WSIT jars are not in war but loaded from Glassfish
        Hide
        sameer_t added a comment -

        Verified that issue is not related to classloading. The issue can be reproduced
        when the WSIT jars are not bundled with the web app and loaded from the
        classpath-prefix.

        Show
        sameer_t added a comment - Verified that issue is not related to classloading. The issue can be reproduced when the WSIT jars are not bundled with the web app and loaded from the classpath-prefix.
        Hide
        sameer_t added a comment -

        1. The server and server-mtom will not (and does not) make any difference. from
        a jax-ws perspective the generated code is the same.
        I verified and reproduced the error after changing it to server-mtom

        2. Regarding prodviding a "more reproducable" test case, I m not sure what else
        I can provide. It may be giving a 404 if you're using Tomcat.

        3. You are right in that the bug is not reproducable in Tomcat.

        4. P1 opened on Glassfish. Issue is 1330.
        https://glassfish.dev.java.net/issues/show_bug.cgi?id=1330

        Show
        sameer_t added a comment - 1. The server and server-mtom will not (and does not) make any difference. from a jax-ws perspective the generated code is the same. I verified and reproduced the error after changing it to server-mtom 2. Regarding prodviding a "more reproducable" test case, I m not sure what else I can provide. It may be giving a 404 if you're using Tomcat. 3. You are right in that the bug is not reproducable in Tomcat. 4. P1 opened on Glassfish. Issue is 1330. https://glassfish.dev.java.net/issues/show_bug.cgi?id=1330
        Hide
        sameer_t added a comment -

        Vijay looking at G/F issue 1330

        Show
        sameer_t added a comment - Vijay looking at G/F issue 1330
        Hide
        mmatula added a comment -

        This issue was fixed before we created 1.0 branch, so the fix is in 1.0 ->
        setting target milestone to say so.

        Show
        mmatula added a comment - This issue was fixed before we created 1.0 branch, so the fix is in 1.0 -> setting target milestone to say so.

          People

          • Assignee:
            venu
            Reporter:
            sameer_t
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: