Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

During the pilot, a service's particular error or alternate login page will have an additional button called "Try authenticating via Touchstone". So for example, if you try to log in to Stellar and your certificate does not work or you do not have one, you currently get the page below.
When the Touchstone pilot goes live, there will be an additional section underneath the current MIT Community Users section on the page below. I pulled an example screenshot from the stellar-dev.mit.edu web site. (See second attachment.) I'll try to put this in the wiki later today.

During the initial phase of the pilot the pilot applications will always require an explicit customer action to "try Touchstone" if login fails by default. It should never re-direct there automatically, unless the user has at least once chosen to use Touchstone and set explicit preferences for their use of Touchstone.
 
Here is a screen shot of what a user of Stellar will see if a certificate is not presented to Stellar when logging in:
 





...

MIT X.509 Certificates are not going away in the forseeable future. They are used by many web sites on campus and even if all web sites decide to transition to MIT Touchstone it will likely take several years for all of the web sites to make such a transition given time and budget contraints.

User should also remember that when properly used certifcates provide a better defence from having your account compromised by phishing attacks or other mechanims than simply using passwords. MIT Touchstone supports username and password authentication only because certificates and other strong authentication technologies cannot be used on all systems everwhere in the world today.

b) What if I set this up on my office computer? Does it work for my home computer too? What about if I use a computer at an internet cafe?

By offering users a variety of mechanisms to authenticate when using MIT Touchstone, users will be able to use MIT Touchstone enabled web applications from a wide variety of locations, be it home, office, or even while using a computer located in an internet cafe or at an airport kiosk machine. However, the authentication preference which the user may select is specific to the machine and browser. This means that a user may might set a preference to use Kerberos tickets on the office computer while having a preference to use certificates from the home computer. The only situations where the user's preference will persist across machines is when using the Athena computing environment or WIN.MIT.EDU.

...

The only password that can be used with Touchstone is your Kerberos password. This is the same password that you use to access your MIT email using Webmail or native clients. The rules for managing your password are not affected by Touchstone in any way. The MIT Touchstone references IS&T's "Creating and Using Your MIT Kerberos Identity". It does  The help page does not currently reference IS&T's Guidelines for Choosing a Password page nor does it reference IS&T's Changing Your Password page, please let us know if you think these links should be added to the MIT Touchstone help page.

d) If I don't have to use certificates any more, why did you make me get a certificate that expires in 2026?

MIT Touchstone is in its early phase of deployment. You are likely to need certificates to authenticate to other web applications at MIT for the foreseeable future.

User should also remember that when properly used certifcates provide a better defence from having your account compromised by phishing attacks or other mechanims than simply using passwords. MIT Touchstone supports username and password authentication only because certificates and other strong authentication technologies cannot be used on all systems everwhere in the world today.

3) The product presents a set of choices for a person to make before they can go forward, but it doesn't give them criteria for making the choices. For example, they are faced with deciding between

...

4) Paul points out that it may be difficult for clients to know whether they are having difficulties with Touchstone, or a different product/service to which it provides access. If the Help Desk identified the problem as a Touchstone issue, what items of information is it useful for us to collect in order to escalate?

  1. What is the name of the customer?
  2. What was the time and date when the problem occurred?
  3. What URL was the user trying to access?
  4. What browser was being used? (Brand and version)
  5. What application was the user trying to access?
  6. What machine was being used when trying to access the URL? (Physical location, hostname, IP address if known)
  7. Which authentication method(s) did the user attempt to use? (username / password, certificate, existing tickets)
  8. What error message was displayed?

5) Is there a written list of resources in particular URLs that will help answer questions? Also, we currently have no screen shots or other reference material. Once the pages are available, it is still helpful to have screen shots of things that clients can see, but which we as consultants might not readily be able to duplicate on our own screens. Is there a way for us to get these?

The Touchstone help page can be found at https://idp.mit.edu/help.html\\Image Removed

https://idp.mit.edu/auth-options  - This is the application that staff should normally use to determine if Touchstone is functional at this time.

We are also working on a more comprehensive test page which can be found at http://touchstone-tester.mit.edu/. At this time we are concentrating on the mechanics of testing the underlying components. As we complete that phase we will focus on improve the UI and making the page more understandable and functional.

The current default MIT Touchstone login page: Image Added

The following page is normally briefly displayed to a user as the system redirects the user's browser back to the originally requested URL when the user has successfully authenticated to the MIT Touchstone login server. If the user is on a slow network link this page may display for longer than the user expects. Image Added
It is possible for the user to encounter the following error page. This should be very rare. I obtained this screen shot by using the Firefox extension "Tamper Data" and modifying the contents of the data being sent back to the login server when logging in using my username and password. Image Added