Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-8118

<key-passwords> in jboss-wsse-client.xml does not work.

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • EAP_EWP 5.2.0
    • EAP_EWP 5.1.1
    • Web Services
    • None
    • Hide

      1. Create a keystore with a private key that has a different password than the keystore:
      keytool -genkey -alias mykey -keypass changeit -storepass changeit2 -keystore client.keystore

      2. Create a jboss-wsse-client.xml config with <key-passwords>
      3. Set up a WS client that uses the WSS config.

      Show
      1. Create a keystore with a private key that has a different password than the keystore: keytool -genkey -alias mykey -keypass changeit -storepass changeit2 -keystore client.keystore 2. Create a jboss-wsse-client.xml config with <key-passwords> 3. Set up a WS client that uses the WSS config.
    • Release Notes
    • Hide
      A keystore can contain a private key that has a different password to the password of the keystore. To use the key in a web service client, the key-password pair must be defined in the <key-password> element in the <filename>jboss-wsse-client.xml</filename> configuration file. Previously, the WS client or WS endpoint that used the configuration file did not process the <key-password> element as the jbossws service failed to pick up the element. The service now detects and picks up the <key-password> element as expected and the problem no longer occurs.
      Show
      A keystore can contain a private key that has a different password to the password of the keystore. To use the key in a web service client, the key-password pair must be defined in the <key-password> element in the <filename>jboss-wsse-client.xml</filename> configuration file. Previously, the WS client or WS endpoint that used the configuration file did not process the <key-password> element as the jbossws service failed to pick up the element. The service now detects and picks up the <key-password> element as expected and the problem no longer occurs.
    • Documented as Resolved Issue
    • NEW

    Description

      When you have a private key in a keystore that has a different password than the keystore itself, then you need to specify that password using the <key-passwords> element in jboss-wsse-client.xml. This element is not picket up starting with EAP 5.1.1. This is a regression from JBPAPP-5589.

      Attachments

        Issue Links

          blocks

          Task - Represents a small unit of work that is not end-user facing. JBPAPP-9494 [JBossWS] Release and upgrade JBossWS Native for EAP 5.2.0

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Feature Request - Feature requests from customers and/or users JBPAPP-5589 JBossWS - Allow for centralized ws-security configuration from jaas security domain

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              rh-ee-klape Kyle Lape
              rh-ee-klape Kyle Lape
              Eva Kopalova Eva Kopalova (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: