Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    SreekanthMezzylabs
    @SreekanthMezzylabs
    hi
    Łukasz Dywicki
    @splatch
    good evening :-)
    Łukasz Dywicki
    @splatch
    hey, I just commited very first draft of authentication stuff: https://github.com/Code-House/smarthome/tree/esh-authz it covers just username/password.
    Łukasz Dywicki
    @splatch
    @kaikreuzer @maggu2810 ^^
    @@all
    just testing
    Kai Kreuzer
    @kaikreuzer
    Cool, could you maybe also sketch your ideas on eclipse/smarthome#579, so that it is clear where you are heading (using login screen and http session ids / oauth tokens, etc.).
    Łukasz Dywicki
    @splatch
    yes, I can add description there to provide input for discussion, not sure if it's more handy to host it there or in mailing list, regarding sessions - this would be depend on framework used, ie. it could be done via http basic at jersey layer in simplest case and via login screens/sessions in more advanced. Regarding oauth, this is conflicting scenario, cause running instance of such software is in fact an resource server and most likely will have its own user database
    Kai Kreuzer
    @kaikreuzer
    I think the issue is a good place to discuss. I am not sure if I understand why oauth is conflicting; what is the big difference between a session id and an access token from a resource pov? You need some internal service that can validate it and provide you the role of the requestor. The way a token gets issued is different to session ids, though, I agree.
    Łukasz Dywicki
    @splatch
    @kaikreuzer I used conflicting scenario in context of oauth cause what we actually need is an resource server or oauth server, not a typical "login with oauth". This may be just input for ESH oauth backend to initialize some account.
    Łukasz Dywicki
    @splatch
    good morning :)
    I have question about dynamic channels and posting updates to these
    is anyone here?
    @kaikreuzer @maggu2810 ping
    Kai Kreuzer
    @kaikreuzer
    @splatch No, usually there is no one here as you can see - it isn't one of the official support channels... Better use the Eclipse Forum for questions!
    Jonathan B
    @mochi-co
    Hey guys, having a weird problem with Paho MQTT and I wasn't sure where to go, I figured smart-home was probably the closest bet... I keep getting "[net] logic stopped" after a seemingly arbitrary amount of time
    Sometimes it happens immediately after connecting, other times it'll stay up for an hour
    (using Mosquitto)
    Sorry, more specifically- PAHO Go MQTT client
    And I just noticed nobody has talked in here for 2 years so maybe not
    Kai Kreuzer
    @kaikreuzer
    Hey @mochihub I am afraid, this indeed isn't the right chat for Paho - probably best if you try their mailing list at https://accounts.eclipse.org/mailing-list/paho-dev
    Łukasz Dywicki
    @splatch
    hi there :)
    does anyone tracks this channel?
    Kai Kreuzer
    @kaikreuzer
    I do. I just cannot promise to also answer here :-)
    Łukasz Dywicki
    @splatch
    @kaikreuzer there is one thing - ds annotations, I see they are used in mix, some modules seems to generate descriptor, some seems to maintain descriptors in scm, what is overall direction there? Second question - any plans on DS update? :-)
    Henning Treu
    @htreu
    hi @splatch. the direction for DS is to use the annotations and let the build script generate the descriptors. We port the existing static XML's to annotations every once in a while. So the goal is to have them all generated.
    Łukasz Dywicki
    @splatch
    @htreu point noted, I was a bit confused when I tried to use annotations and then got into conflicts with existing files (same component generated from annotations and maintained in GIT). I cleared it out before hand. Still there is open question about DS update - version 1.2 does not support abstract classes making them well, useless from DI point of view.
    Henning Treu
    @htreu
    Since the DS version is specified by the OSGi version which is set to 4.2 for ESH we will not update any time soon. There are solutions based on ESH which require an OSGi version 4.2
    Łukasz Dywicki
    @splatch
    yeah, I'm aware of 4.2 condition, but DS implementations are not that strongly dependant on core of the spec