Hi all,<br><br>Please excuse my ignorance about Shibboleth and SAML, I've done some reading on the subject but I'm still not sure how to accomplish what I'd like to do. I'm writing a web-based application, for myself and for a few friends,which will interact with my university's student portal:<br>
<br><a href="https://acadinfo.wustl.edu/">https://acadinfo.wustl.edu/</a><br><br>I believe that our single sign on system is based on Shibboleth because of what I've observed in the signing process, and because the WUSTL CONNECT website says that's what they're using. <br>
<br>In the past, student-written applications that interact with this site (e.g. iPhone apps) have procured credentials by simulating a form submission through the web page and following a bunch of redirects. I have a solution using Python's version of Mechanize which does this, but it's pretty ugly and visits no fewer than 7 URLs before logging in. While screen scraping the actual website is probably unavoidable, I want to know if there's a better way to authenticate.<br>
<br>I'd also like to know if there's a way that I can avoid storing user credentials in a recoverable form, perhaps by getting some kind of auth token and keeping that instead. <br><br>My investigations have found the following URL endpoint that's part of the login process, but I can't get any of the command line shibboleth clients to work with it:<br>
<a href="https://login.wustl.edu/idp/profile/SAML2/POST/SSO">https://login.wustl.edu/idp/profile/SAML2/POST/SSO</a><br><br>Any tips would be much appreciated :-)<br><br>- Troy<br>