alfred-redmine icon indicating copy to clipboard operation
alfred-redmine copied to clipboard

Support for Redmine behind HTTP Auth.

Open jamesepatrick opened this issue 8 years ago • 6 comments

Hey Jason0x43,

I haven't been able to find a way to connect to a Redmine Instance that is behind Basic HTTP Auth. I was wondering if there way any undocumented way to do this. I tried to connect using user:[email protected] but it errors out when with a message saying that it was unable to connect to the host.

If this isn't currently supported and you are open to adding this, I'd be willing to add this and sent a pull request.

jamesepatrick avatar Nov 18 '16 17:11 jamesepatrick

Just to clarify, you're interested in Basic Auth that's separate from Redmine's own Basic Auth (which is just an alternative to using an API key)?

jason0x43 avatar Nov 21 '16 02:11 jason0x43

Yep. The HTTP Basic Auth, not Redmine's Basic Auth.

jamesepatrick avatar Nov 21 '16 17:11 jamesepatrick

Hmmm...ok. Redmine supports HTTP Basic Auth, and there's some allowance for using it in the workflow, but just enough to figure out the user's API key (because ideally the workflow shouldn't store a username and password). I'll need to add something to support a completely separate set of basic auth credentials, and preferably to store them in the keychain.

jason0x43 avatar Nov 21 '16 18:11 jason0x43

Hey Jason. I meant as in a password protected reverse proxy using a web server (eg Apache).

jamesepatrick avatar Nov 21 '16 18:11 jamesepatrick

Yeah, that's why it needs to support separate (non-Redmine) credentials.

jason0x43 avatar Nov 21 '16 18:11 jason0x43

Totally doable.

jason0x43 avatar Nov 21 '16 18:11 jason0x43