[jira] [Work logged] (ARTEMIS-3042) Official Docker Multistage Build as well as an official Docker image.
[ https://issues.apache.org/jira/browse/ARTEMIS-3042?focusedWorklogId=828956&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-828956 ] ASF GitHub Bot logged work on ARTEMIS-3042: --- Author: ASF GitHub Bot Created on: 25/Nov/22 13:19 Start Date: 25/Nov/22 13:19 Worklog Time Spent: 10m Work Description: gtully opened a new pull request, #4297: URL: https://github.com/apache/activemq-artemis/pull/4297 This module builds an OCI image tar, based around a broker Main class, that can be configured with property files and/or xml. The intent is to be a simple as possible but still be useful. See the README.md for details. Issue Time Tracking --- Worklog Id: (was: 828956) Remaining Estimate: 0h Time Spent: 10m > Official Docker Multistage Build as well as an official Docker image. > - > > Key: ARTEMIS-3042 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3042 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: John Behm >Priority: Minor > Labels: docker,, dockerfile,, kubernetes > Time Spent: 10m > Remaining Estimate: 0h > > It would be rather convenient to get people up and running with an easy to > build or to setup Docker image that automatically builds the project from > source, discards the build container and moves the necessary files over to > the final container that can simply be started. > The current docker image build is not really user firendly or convenient at > all. > > https://github.com/apache/activemq-artemis/tree/master/artemis-docker > The whole setup process of artemis in a containerized environment is very > far from even good. > The hurdle of using this software is gigantic, as the configuration is so > complex, one will not be able to do this within one month without having gone > through the whole documentation multiple times. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9102) HTTP Proxy Exclusions are not applied to ActiveMQ Connections
[
https://issues.apache.org/jira/browse/AMQ-9102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17638722#comment-17638722
]
ASF subversion and git services commented on AMQ-9102:
--
Commit a530142fd5e5237efa254fd222be52af5bdd8ac3 in activemq's branch
refs/heads/main from Jean-Baptiste Onofré
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=a530142fd ]
Merge pull request #942 from jbonofre/AMQ-9102
[AMQ-9102] Add http.nonProxyHost support in HTTP transport
> HTTP Proxy Exclusions are not applied to ActiveMQ Connections
> -
>
> Key: AMQ-9102
> URL: https://issues.apache.org/jira/browse/AMQ-9102
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.16.3
>Reporter: Stephan Wagner
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 5.18.0, 5.17.3
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> In [this
> commit|https://github.com/apache/activemq/commit/1ced34a383c5e3910c582fd3bfd720a8f6fcde32]
> basic HTTP-Proxy support using the default properties was added to ActiveMQ,
> however the implementation does not account for the [exclusion list in
> property
> "http.nonProxyHosts"|https://docs.oracle.com/javase/8/docs/technotes/guides/net/proxies.html],
> which leads to issues in environments that use a system proxy, but exclude
> certain targets from proxy usage.
> Given the implementation in {{HttpTransportSupport}} (in particular
> {{{}getProxyHost(){}}}) and {{HttpClientTransport}} (in particular creation
> of the HTTP Client) there is no way to use ActiveMQ in a mixed
> non-proxy/proxy environment.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (AMQ-9102) HTTP Proxy Exclusions are not applied to ActiveMQ Connections
[
https://issues.apache.org/jira/browse/AMQ-9102?focusedWorklogId=828998&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-828998
]
ASF GitHub Bot logged work on AMQ-9102:
---
Author: ASF GitHub Bot
Created on: 25/Nov/22 17:24
Start Date: 25/Nov/22 17:24
Worklog Time Spent: 10m
Work Description: jbonofre merged PR #942:
URL: https://github.com/apache/activemq/pull/942
Issue Time Tracking
---
Worklog Id: (was: 828998)
Time Spent: 0.5h (was: 20m)
> HTTP Proxy Exclusions are not applied to ActiveMQ Connections
> -
>
> Key: AMQ-9102
> URL: https://issues.apache.org/jira/browse/AMQ-9102
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.16.3
>Reporter: Stephan Wagner
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 5.18.0, 5.17.3
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> In [this
> commit|https://github.com/apache/activemq/commit/1ced34a383c5e3910c582fd3bfd720a8f6fcde32]
> basic HTTP-Proxy support using the default properties was added to ActiveMQ,
> however the implementation does not account for the [exclusion list in
> property
> "http.nonProxyHosts"|https://docs.oracle.com/javase/8/docs/technotes/guides/net/proxies.html],
> which leads to issues in environments that use a system proxy, but exclude
> certain targets from proxy usage.
> Given the implementation in {{HttpTransportSupport}} (in particular
> {{{}getProxyHost(){}}}) and {{HttpClientTransport}} (in particular creation
> of the HTTP Client) there is no way to use ActiveMQ in a mixed
> non-proxy/proxy environment.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (AMQ-9102) HTTP Proxy Exclusions are not applied to ActiveMQ Connections
[
https://issues.apache.org/jira/browse/AMQ-9102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17638721#comment-17638721
]
ASF subversion and git services commented on AMQ-9102:
--
Commit 44a5539afc689f23c63a0d2e1786b48c0e52f3c3 in activemq's branch
refs/heads/main from Jean-Baptiste Onofré
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=44a5539af ]
[AMQ-9102] Add http.nonProxyHost support in HTTP transport
> HTTP Proxy Exclusions are not applied to ActiveMQ Connections
> -
>
> Key: AMQ-9102
> URL: https://issues.apache.org/jira/browse/AMQ-9102
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.16.3
>Reporter: Stephan Wagner
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 5.18.0, 5.17.3
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> In [this
> commit|https://github.com/apache/activemq/commit/1ced34a383c5e3910c582fd3bfd720a8f6fcde32]
> basic HTTP-Proxy support using the default properties was added to ActiveMQ,
> however the implementation does not account for the [exclusion list in
> property
> "http.nonProxyHosts"|https://docs.oracle.com/javase/8/docs/technotes/guides/net/proxies.html],
> which leads to issues in environments that use a system proxy, but exclude
> certain targets from proxy usage.
> Given the implementation in {{HttpTransportSupport}} (in particular
> {{{}getProxyHost(){}}}) and {{HttpClientTransport}} (in particular creation
> of the HTTP Client) there is no way to use ActiveMQ in a mixed
> non-proxy/proxy environment.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (AMQ-9102) HTTP Proxy Exclusions are not applied to ActiveMQ Connections
[
https://issues.apache.org/jira/browse/AMQ-9102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17638724#comment-17638724
]
ASF subversion and git services commented on AMQ-9102:
--
Commit 60e79ed3d5aef3c3d9557d8b86e7a21c5a3ae2a1 in activemq's branch
refs/heads/activemq-5.17.x from Jean-Baptiste Onofré
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=60e79ed3d ]
[AMQ-9102] Add http.nonProxyHost support in HTTP transport
(cherry picked from commit 44a5539afc689f23c63a0d2e1786b48c0e52f3c3)
> HTTP Proxy Exclusions are not applied to ActiveMQ Connections
> -
>
> Key: AMQ-9102
> URL: https://issues.apache.org/jira/browse/AMQ-9102
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.16.3
>Reporter: Stephan Wagner
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 5.18.0, 5.17.3
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> In [this
> commit|https://github.com/apache/activemq/commit/1ced34a383c5e3910c582fd3bfd720a8f6fcde32]
> basic HTTP-Proxy support using the default properties was added to ActiveMQ,
> however the implementation does not account for the [exclusion list in
> property
> "http.nonProxyHosts"|https://docs.oracle.com/javase/8/docs/technotes/guides/net/proxies.html],
> which leads to issues in environments that use a system proxy, but exclude
> certain targets from proxy usage.
> Given the implementation in {{HttpTransportSupport}} (in particular
> {{{}getProxyHost(){}}}) and {{HttpClientTransport}} (in particular creation
> of the HTTP Client) there is no way to use ActiveMQ in a mixed
> non-proxy/proxy environment.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (AMQ-9102) HTTP Proxy Exclusions are not applied to ActiveMQ Connections
[
https://issues.apache.org/jira/browse/AMQ-9102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré resolved AMQ-9102.
---
Resolution: Fixed
> HTTP Proxy Exclusions are not applied to ActiveMQ Connections
> -
>
> Key: AMQ-9102
> URL: https://issues.apache.org/jira/browse/AMQ-9102
> Project: ActiveMQ
> Issue Type: Bug
>Affects Versions: 5.16.3
>Reporter: Stephan Wagner
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 5.18.0, 5.17.3
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> In [this
> commit|https://github.com/apache/activemq/commit/1ced34a383c5e3910c582fd3bfd720a8f6fcde32]
> basic HTTP-Proxy support using the default properties was added to ActiveMQ,
> however the implementation does not account for the [exclusion list in
> property
> "http.nonProxyHosts"|https://docs.oracle.com/javase/8/docs/technotes/guides/net/proxies.html],
> which leads to issues in environments that use a system proxy, but exclude
> certain targets from proxy usage.
> Given the implementation in {{HttpTransportSupport}} (in particular
> {{{}getProxyHost(){}}}) and {{HttpClientTransport}} (in particular creation
> of the HTTP Client) there is no way to use ActiveMQ in a mixed
> non-proxy/proxy environment.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-3168) JAAS login module to convert existing Principal to an Artemis UserPrincipal
[ https://issues.apache.org/jira/browse/ARTEMIS-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17638727#comment-17638727 ] ASF subversion and git services commented on ARTEMIS-3168: -- Commit 7d537882ca4f2a00cc1cd081b256872c77e4604f in activemq-artemis's branch refs/heads/main from Gary Tully [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=7d537882ca ] ARTEMIS-3168 - fix test, ref to auto created pem before creation complete > JAAS login module to convert existing Principal to an Artemis UserPrincipal > --- > > Key: ARTEMIS-3168 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3168 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: JAAS >Affects Versions: 2.17.0 >Reporter: Gary Tully >Assignee: Gary Tully >Priority: Minor > Fix For: 2.18.0 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > Artemis verifies that an authenticated subject always has an Artemis > UserPrincipal which makes sense. All of the existing login modules produce > UserPrincipals. However login modules are plugable and varied. Some allow > some control of the role principal classes that they support but are less > likely to allow the Principal classes to be replaced. > For the hawtio console for example, the configurable RolePrincipal classes > allow both karaf and Artemis to co-exist and share role names. They can also > agree on the UserPrincipal class. However in chaining login modules where > there is not agreement on the UserPrincipal, it is useful to be able to > convert to the Artemis expected format at the end of the login process. > A simple PrincipalConversionLoginModule configured with the list of class > names to match against, would suffice here. A known validated XPrincipal(Bob) > can then appear in Artemis as UserPrincipal(Bob) without prior agreement, > making any login module a candidate for inclusion in the Artemis > login.config. -- This message was sent by Atlassian Jira (v8.20.10#820010)
