Doesn't work on secure clusters

[timrcase]

This doesn't work on a secure cluster. I'm assuming this is by design since there is nowhere to enter credentials in order to access the JobTracker.

[bgreenlee]

Yeah, I wrote this originally for our internal cluster at Etsy, which is behind a VPN and has no additional authentication. How is the authentication done in a secure cluster? I could make an attempt at adding it, although I'd be flying blind.

[timrcase]

A cluster running in secure mode uses Kerberos, but I'm 99% sure that it is handled on the web server as part of the user's session so you would just need to authenticate the user to the server.

[bgreenlee]

Does it work if you put it in the JobTracker URL? e.g. http://:@some.com/.... I know that's not ideal, but that will at least tell me if it's just Basic Auth.

[timrcase]

Unfortunately, that didn't work. Based on the redirects I'm seeing it looks like we might be proxying JT with Hue. I don't think this is going to be easy, but it could also be because of our environment.

[bgreenlee]

Well, if you can provide me code (in any language) that successfully grabs the JobTracker HTML in your environment, I can probably implement it.

[timrcase]

I'll see what I can do. Do you have a preference of language?

[bgreenlee]

No preference. Just not brainf*ck, please. :)