[CAMEL-14143] Slack Component: Consumer does not retrieve user details on message event

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.24.3, 3.0.0, 2.25.0
• Component/s: camel-slack
• Patch Info: Patch Available
• Estimated Complexity: Novice
• Assignee: Andrea Cosentino
• Reporter: Andy Krohg
• Created: 05/Nov/19 20:10
• Updated: 06/Nov/19 10:31
• Resolved: 06/Nov/19 10:31

Description

The JSON object that Slack delivers for message events no longer sends a username attribute; it issues the user's GUID in the user field. For example:

 

{
        "client_msg_id":"6d1d3108-cf2a-4475-941c-0dd70200e88a",
        "type":"message",
        "text":"hello",
        "user":"UMQLDBWQY",
        "ts":"1572977454.000200",
        "team":"T0383HKJ0"
}

The SlackEndpoint class still looks for the username attribute when creating the exchange, so the SlackMessage object comes out pretty bare.

    public Exchange createExchange(ExchangePattern pattern, JsonObject object) {
        Exchange exchange = super.createExchange(pattern);
        SlackMessage slackMessage = new SlackMessage();
        String text = object.getString("text");
        String username = object.getString("username");
        slackMessage.setText(text);
        slackMessage.setUsername(username);
        if (ObjectHelper.isNotEmpty(object.get("icons"))) {
            JsonObject icons = object.getMap("icons");
            if (ObjectHelper.isNotEmpty(icons.get("emoji"))) {
                slackMessage.setIconEmoji(icons.getString("emoji"));
            }
        }
        Message message = exchange.getIn();
        message.setBody(slackMessage);
        return exchange;
    }

I've attached a .patch that retrieves the user's GUID instead, so it's at least available if people using this component want to look up the username with the users.info API.