Passing XMPP client authentication to run hubot scripts #1297

Open
bwcawa opened this Issue Feb 3, 2014 · 1 comment

Projects

None yet

2 participants

@bwcawa
bwcawa commented Feb 3, 2014

Hello,

We are using a XMPP client and server. Hubot is logged into a conference room using a Jenkins coffee script configured to talk with our Jenkins build server. I’ve got a question regarding running hubot scripts.

If we currently run “hubot jenkins list” followed by “hubot jenkins b 1” and a jenkins build kicks off as the hubot user/password. What we would like to happen is the user logged into the XMPP client as that user can the following command run as that user? (“hubot jenkins b 1”) without extra logins?

If the above questions are not currently in source will they be? When?

@technicalpickles
Member

If we currently run “hubot jenkins list” followed by “hubot jenkins b 1” and a jenkins build kicks off as the hubot user/password. What we would like to happen is the user logged into the XMPP client as that user can the following command run as that user? (“hubot jenkins b 1”) without extra logins?

The way the current script at https://github.com/github/hubot-scripts/blob/master/src/scripts/jenkins.coffee is that there's a single authentication, so it's going to always appear as coming from hubot.

I'm not really familiar with janky at all, but the script would have access to some information about the user sending the command (see msg.message.user object). If janky's http end points accept extra metadata, it'd be possible to pass user and room information along.

At GitHub, we've written janky as a layer that sits on top of jenkins, specifically designed to interact with hubot. Might be worth checking that out to see if it fits your needs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment