Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-10159

Sticky authentication is not working correctly

    XMLWordPrintable

Details

    Description

      Sticky authentication and connection sharing is not working correctly. When an object such as an EJB proxy, naming context, or transaction controller (like UserTransaction) is looked up via JNDI where the context has authentication configuration associated with it, that configuration should be sticky to the EJB proxy, context, or transaction controller. When such entities are looked up without security information, then authentication information should be looked up from the calling context's security configuration.

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-8635 Recovery doesn't work when transaction is propagated thru EJB remoting

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-9654 Scoped EJB client context from EAP 7.1 can't invoke stateful beans on EAP 7.0

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-9662 Invocations on UserTransaction obtained from InitialContext don't take user credentials into account

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-9692 Remote-outbound-connection with legacy-style configuration only allows JBOSS-LOCAL-USER auth mechanism

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-9713 Remote outbound connection with authentication-context cannot be used for remote EJB calls

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-10090 Attribute allow-sasl-mechanisms is ignored in Elytron Authentication Configuration

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified
          causes

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-10284 Transaction invoked by client does not finish commitment in ejb-multi-server quickstart when using scoped context

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is caused by

          Bug - A problem that impairs or prevents the functions of the product. EJBCLIENT-210 Sticky authentication should be keyed by URI + auth conf

          • 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.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. REM3-266 Connection sharing APIs are incorrect

          • 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.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. WFNC-27 Naming providers need to have a sticky authentication association

          • 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.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. WFTC-18 Use sticky auth from naming context when available

          • 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.
          • Resolved

          Activity

            People

              dlloyd@redhat.com David Lloyd
              dlloyd@redhat.com David Lloyd
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: