[ 
https://issues.apache.org/jira/browse/ARTEMIS-5316?focusedWorklogId=959190&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-959190
 ]

ASF GitHub Bot logged work on ARTEMIS-5316:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 27/Feb/25 13:57
            Start Date: 27/Feb/25 13:57
    Worklog Time Spent: 10m 
      Work Description: clebertsuconic commented on code in PR #5535:
URL: https://github.com/apache/activemq-artemis/pull/5535#discussion_r1973632501


##########
artemis-protocols/artemis-amqp-protocol/src/main/java/org/apache/activemq/artemis/protocol/amqp/connect/AMQPBrokerConnection.java:
##########
@@ -1204,6 +1206,47 @@ public static boolean isApplicable(final NettyConnection 
connection) {
       }
    }
 
+   private static class XOAuth2SASLMechanism implements ClientSASL {

Review Comment:
   Isn't there a way to write a Unit Test for this?





Issue Time Tracking
-------------------

    Worklog Id:     (was: 959190)
    Time Spent: 20m  (was: 10m)

> Support for SASL XOAUTH2 Mechanism in Broker Connection
> -------------------------------------------------------
>
>                 Key: ARTEMIS-5316
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-5316
>             Project: ActiveMQ Artemis
>          Issue Type: New Feature
>            Reporter: Tomasz Ɓukasiewicz
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> There is a need to support XOAUTH2 authentication between two AMQP brokers, 
> as the existing mechanisms are not sufficiently secure for certain use cases. 
> Currently, Artemis does not support this authentication method on the client 
> side, and the SaslFactory implementation is both private and final, making it 
> impossible to extend.
> To address this, an XOAuth2SASLMechanism should be implemented within the 
> AMQPBrokerConnection class and integrated into the SaslFactory. The new SASL 
> mechanism should return its name as "XOAUTH2" and include the appropriate 
> authentication headers.
> A working example of this approach has been successfully tested with the 
> Solace broker:
> {code:java}
> @Override
> public byte[] getInitialResponse() {
>    String response = String.format("user=%s\u0001auth=Bearer %s\u0001\u0001", 
> userName, token);
>    return response.getBytes(StandardCharsets.UTF_8);
> }
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact


Reply via email to