Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [kura-dev] mandatory MQTT username/password?
Thanks for the quick feedback Dave. 
So I did patch my Kura install to allow username and passwords to be NULL. I can now connect to AWS IOT (woohoo!) but my next issue is the following: CloudService does use $EDC prefixed topics, and AWS does not like that [1].
I can easily workaround that problem by disabling the CloudService component, but this can't be done from the UI. I wonder if it would make sense to have the ability to disable the CloudService from the UI (just like eg the ClockService?) and/or to make the $EDC prefix a setting. I understand this will break the existing workflow for Eurotech customers, but that shouldn't be too big of an issue for others, and it would actually make sense IMO to allow people to chose "where" they want their control messages to be. Unless I'm mistaken, there would just need to be the "topic.control-prefix" key exposed in the metatype file for the CloudService component. Would you agree that the "control prefix" needs to be customizable?

Thanks
Benjamin 


[1] - https://docs.aws.amazon.com/iot/latest/developerguide/topics.html ("Any topics beginning with '$' are considered reserved and are not supported for publishing and subscribing" but it's actually more strict than that, since they just kill the connection)





Benjamin Cabé

Eclipse Foundation
+33 (0) 619196101

De : <kura-dev-bounces@xxxxxxxxxxx> on behalf of "Woodard, David" <David.Woodard@xxxxxxxxxxxx>
Répondre à : Kura Developers mailing list <kura-dev@xxxxxxxxxxx>
Date : jeudi 15 octobre 2015 15:07
À : Kura Developers mailing list <kura-dev@xxxxxxxxxxx>
Objet : Re: [kura-dev] mandatory MQTT username/password?

Hello Benjamin,

This is simply a legacy feature that was included when we first forked our code base for the Kura project. As you say, it is generally not an issue as brokers not requiring authentication will ignore the default username/password, so we haven’t changed the requirement. We do need to review this requirement if you are having problems with AWS. If you have a patch we would certainly review it. 

Thanks,
--Dave

On Oct 15, 2015, at 06:07, Benjamin Cabé <benjamin@xxxxxxxxxxx> wrote:

Hi,

Is there a reason why the MqttDataTransport must be given a username and password? While this has not given me any trouble in the past since most "unsecure" brokers would just ignore the given credentials, I have troubles connecting to AWS IOT since the dummy username/password actually does cause an authentication issue :(

FWIW I am happy to propose a patch if you think it's worth fixing.

Thanks
Benjamin –


Benjamin Cabé

Eclipse Foundation
+33 (0) 619196101
_______________________________________________
kura-dev mailing list
kura-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/kura-dev

_______________________________________________ kura-dev mailing list kura-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/kura-dev

Back to the top