camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Arthur (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CAMEL-6348) SecurityException in HDFS producer/consumer when no security configuration is present
Date Fri, 10 May 2013 13:05:16 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-6348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

David Arthur updated CAMEL-6348:
--------------------------------

    Attachment: CAMEL-6348.patch

Not sure how you guys prefer patches. This was generated with "git diff --no-prefix HEAD"
from the camel-hdfs directory. Let me know if you prefer something else.
                
> SecurityException in HDFS producer/consumer when no security configuration is present
> -------------------------------------------------------------------------------------
>
>                 Key: CAMEL-6348
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6348
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-hdfs
>    Affects Versions: 2.11.0
>            Reporter: David Arthur
>             Fix For: 2.10.5, 2.11.1, 2.12.0
>
>         Attachments: CAMEL-6348.patch
>
>
> In the HdfsProducer and HdfsConsumer classes, there are calls to get the current security
configuration
> {code}
> Configuration auth = Configuration.getConfiguration();
> {code}
>  
> in order to later reset them after HDFS tramples the system with its own config. However,
if no security configuration was set, this throws a SecurityException like:
> {code}
> Exception in thread "main" org.apache.camel.FailedToCreateProducerException: Failed to
create Producer for endpoint: Endpoint[hdfs://localhost:50001/tmp/camel/?splitStrategy=MESSAGES%3A4].
Reason: java.lang.SecurityException: Unable to locate a login configuration
> {code}
> My current workaround is to set the system property "java.security.auth.login.config"
to an empty file. 
> It seems like the code should check if a configuration exists before fetching it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message