Which websites and applications need to move to SAML by August 31, 2018?
University IT will move the following websites to SAML by December 15, 2018. If you own one of these sites, you do not need to take any action:
- Websites accessing the AFS (FileDrawers) service (Stanford WebAFS)
- Websites hosted on the central web servers (web.stanford.edu)
- Websites hosted on Stanford Sites
- The UIT proxy service
If your website or application uses WebAuth for authentication and is not listed above, you need to move to SAML by August 31, 2018.
How can I tell whether my website or application uses WebAuth?
Open a private browser window, then open your website or application in that window. Your site uses WebAuth if the URL weblogin.stanford.edu appears in the browser's address bar during authentication.
How do I change the authentication on my website or application from WebAuth to SAML?
For information and instructions on how to move to SAML, see the SAML (Authentication) webpage.
What happens if I don't migrate my website or application to SAML by August 31, 2018?
Your website or application will stop working after August 31, 2018, if it uses legacy WebAuth for authentication, unless you request a deadline extension. For instructions on how to request an extension, see "What should I do if I can't move my website or application to SAML by August 31, 2018?" below.
What should I do if I can't move my website or application to SAML by August 31, 2018?
First, decide whether your website or application needs authentication. If it does not need authentication, then remove WebAuth.
If your website or application does need authentication but you can't migrate to SAML by August 31, deadline extensions are available on a case-by-case basis. The first extension moves the deadline to October 15, 2018, and the second (and final) extension moves the deadline to December 15, 2018.
Submit a Help request to discuss an extension with the WebAuth support team. In the request, include the following information:
- Application owner contact information
- Technical owner contact information
- URL of your website or application
- Name of WebAuth keytab principal
- Extension date that you want (October 15 or December 15)