Retrieve ISO protected web pages
The presence of a url command, either on the command line or interactively, causes webisoget to retrieve the specified web page. In certain conditions it will use content in that page to retrieve a second page:
The second page may lead in a similar manner to a third and fourth and etc.
Web forms consist of name-value pairs. Webisoget's form file contains descriptions, one line per form, of forms you want to fill out and submit. General syntax is name=value, with entries separated by semicolons.
For example, the form specification
name=query; user=spud; pass=potato;Would submit pubcookie's login form.
Many forms have name-value pairs with default values, hidden fields, for example. Webisoget will automatically fill in any default values.
As with any application using SSL, webisoget allows you to specify a CA file of trusted certificate authorities; certificate and key files containing a certificate to use if a target site requires one. You can also choose to ignore verification of the server's certificate.
A service is often supported by a cluster of several systems, each responding to the same domain name. A weblogin service at "weblogin.ivy.edu" might consist of the servers "wl01.login.ivy.edu", "wl02.login.ivy.edu", ..., "wl05.login.ivy.edu". Webisoget allows you to map the generic cluster name to a specific system in that cluster.
Webisoget supports the most common REST operations,
but cannot help you with the XML.
Webisoget processes commands on the command line in the order they appear. It does NOT read the entire set of arguments before proceeding. If no URL is specified webisoget will process the arguments and wait for interactive commands.
Interactive commands are just like arguments except they don't use the leading dash.
Pubcookie uses several Location redirection and one form (query).
To retrieve a page protected by pubcookie, using the user user with id "spud" and password "potato" use this formfile (spud.login)
name=query; user=spud; pass=potato;
$ webisoget -verbose -out page.txt -formfile spud.login \ -url https://target.ivy.edu/pubcookie_protected_path/
Shibboleth uses several Location redirections, possibly a form at a wayf, and, of course, whatever the IdP's login requirements are.
To retrieve a page protected by shibboleth (with pubcookie), using the user user with id "spud" and password "potato" use this formfile (spud.login)
domain=wayf.incommonfederation.org; origin=urn:mace:incommon:ivy.edu; name=query; user=spud; pass=potato; name=shibboleth; name=; submit_value=Continue; domain=your_idp_domain_name
$ webisoget -verbose -out page.txt -formfile spud.login \ -url https://target.ivy.edu/shibboleth_protected_path/
Google (this is a google openid-connect login) uses a form and some Location redirections. After you're logged in there may be more pages to negotiate. Save yourself trouble and prerelease any attributes you might need.
To accomplish a google openid-connect login using the user user with email "firstname.lastname@example.org" and password "potato" use this formfile (spud.login)
domain=accounts.google.com; Emailemail@example.com; Passwd=potato;
Apache License 2. You are free to copy, use, and modify it to your needs according to the terms of that license.
[an error occurred while processing this directive]
© 1983-2017, University of Washington