> If this is checked by the plugin (e.g. for the first case it asks for a
> username/password) then the request is redirected to the configured Galene
> Server including the immediately generated JWT token.
Ok, so you're ignoring Galene's built-in authentication mechanisms, and
just using short-lived JWTs for everything. That makes sense.
I'm wondering what I could do on the Galene side to simplify your usage.
In particular, would it be useful if you could just do an HTTPS PUT
(properly authentified) in order to update a group definition in order to
avoid sftp? Or perhaps we could have a mode of operation where groups
automagically come into existence if they are required by a properly
authentified token?
-- Juliusz
_______________________________________________
Galene mailing list --
galene@lists.galene.orgTo unsubscribe send an email to
galene-leave@lists.galene.org