qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Rudyy (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-7244) Expose realm qualified authenticate name to messaging clients
Date Mon, 04 Jun 2018 10:52:00 GMT

    [ https://issues.apache.org/jira/browse/QPID-7244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16500053#comment-16500053

Alex Rudyy commented on QPID-7244:

The work is de-scoped from 7.1.0

> Expose realm qualified authenticate name to messaging clients
> -------------------------------------------------------------
>                 Key: QPID-7244
>                 URL: https://issues.apache.org/jira/browse/QPID-7244
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Broker-J
>            Reporter: Keith Wall
>            Priority: Major
>              Labels: Broker-J-Identity
>             Fix For: Future
> We want messaging clients to be capable of publishing messages with the {{JMSXUserId}}
populated with a realm qualified authenticated name.
> To enable this for 0-8..0-10 change message source {{$virtualhostproperties}} to have
an extra header {{authenticatedUser}} which will contain the serialised form of the principal.
  For 1.0, a non-normative (probably qpid specific) connection property could be used by the
open performative (discussion required).
> The Java Broker messageAuthorizationRequired feature must be relaxed to allow either
the the realm qualified form, or bare form. The latter is required for compatibility with
clients which don't support the feature.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message