in reply to Re^2: support for securid login
in thread support for securid login

Ah - I thought you wanted to completely replicate the login, given the securid secret.

If your problem is "only" with replicating the communication and not with some Javascript involved in the browser, the difference must be in the data that gets sent. If all headers are equal (except for the timestamps, and session cookies), then the difference must be in the payload data.

I don't know if SSL certificates get triggered by the URL or only by the host. If they get triggered by the URL, you will have to look into how LWP::UserAgent chooses the fitting certificate(s) to verify that the correct one is chosen..

Replies are listed 'Best First'.
Re^4: support for securid login
by Anonymous Monk on Jun 11, 2013 at 20:32 UTC
    Thank a lot for you responses, Corion. Turns out I had a stupid typo in my config file that the script was reading for the static part of the code (the pin). Once I fixed that, I can successfully login and scrape what I need ;-)