Circumventing a manual HTML login page for "unclassified" websites (automation purposes, credentials

Posted by auramo on Super User See other posts from Super User or by auramo
Published on 2010-05-31T09:27:30Z Indexed on 2010/05/31 11:43 UTC
Read the original article Hit count: 198

Filed under:
|
|
|
|

The IT department just made my life a little bit harder again: they introduced a manual HTML login page for all websites they have not "classified". This means that all the applications which try to access unclassified websites for e.g. downloading plugins do not work. Examples: Eclipse plugin installation, Maven builds etc.

What would be the easiest workaround for this? The best I've come up with is try to extend/customize Ruby's httpproxy.rb that comes with Webrick. I would automate the manual login process whenever that login response page is detected. This sounds quite painful, and I think there might/should be simpler options?

© Super User or respective owner

Related posts about proxy

Related posts about login