You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Otavio Rodolfo Piske (Jira)" <ji...@apache.org> on 2020/07/22 12:38:00 UTC

[jira] [Commented] (CAMEL-15326) camel-slack: incorrect handling of error responses

    [ https://issues.apache.org/jira/browse/CAMEL-15326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17162762#comment-17162762 ] 

Otavio Rodolfo Piske commented on CAMEL-15326:
----------------------------------------------

I have a fix in progress for this issue and I will send a PR for review.

> camel-slack: incorrect handling of error responses
> --------------------------------------------------
>
>                 Key: CAMEL-15326
>                 URL: https://issues.apache.org/jira/browse/CAMEL-15326
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-slack
>    Affects Versions: 3.4.2
>            Reporter: Otavio Rodolfo Piske
>            Priority: Major
>         Attachments: log-when-channels-read-is-missing.txt
>
>
> The consumer on the camel-slack component is not checking for error responses coming from the Slack API. Under some circumstances this can be problematic and hide messages that would be helpful for the user to diagnose problems on his/her setup of the app/bot account. 
> One example that causes this problem is when the user creates a bot and does not give the bot the channels:read scope/permission. In this case the component throws a NullPointerException because it looks for an element on the json response that does not exist. 
>  
> It seems it can also happen when trying to read the channel messages without the channels:history scope, although, in this case the component does not throw any exception.
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)