USPTO should stop the forced logouts from Private PAIR and EFS-Web

When you log in to USPTO’s Private PAIR and EFS-Web system, you have to go through a cumbersome process.  You have to mouse around and find a “crypto certificate” on your hard drive that proves your identity.  You have to wait for a very slow “Java applet” to run, taking some tens of seconds.  And you have to type in a password that is required to contain at least one smiley face (just kidding).  This would not be so bad except that this system logs you out at more or less random times, after anywhere from ten to sixty minutes of inactivity.  A quick trip to the bathroom or coffee machine can lead to your having to log in all over again.  In a normal work day a USPTO customer might be forced to log in again a dozen or more times.

A couple of years ago I surveyed users of PAIR and EFS-Web about this system of forced logouts.  The vast majority of respondents said that for them, this system of forced logouts is a bug, not a feature.  I passed the results of the survey along to USPTO people who are responsible for this system.  Unfortunately in the two years that have passed since this survey, USPTO has not done anything to improve this situation.

More than 90% of respondents said that they find the “forced logout” feature neither important nor valuable.  If USPTO were to change the system so that each user could choose for a particular login session to never get logged out automatically, 81% of the respondents would use that feature sometimes or for nearly all of their login sessions.

You can see the results of the survey here.

Many regular users of the EFS-Web and PAIR systems belong to listservs — the EFS-Web listserv for patent practitioners generally and the PAIR listserv for users of the PAIR system.  (If you use these systems you should join these listservs — you can always unsubscribe later if you wish.)  Many of those who responded to the survey came from one listserv or the other.

What about you?  What would you like to tell the USPTO about your wishes for EFS-Web and Private PAIR?  Post a comment below.

3 thoughts on “USPTO should stop the forced logouts from Private PAIR and EFS-Web

  1. While I don’t like the forced logout, I do understand the need for it. The bigger problem is the use of java to begin with which makes logging in so slow, uses a ridiculous amount of resources of your computer to just upload a file, and breaks easily. It’s a huge time waster. One one computer, I need to click the button to upload the file like a manic person with OCD, and another computer, I have to remember to open Private Pair a few minutes before I actually want to use it, because it takes that long until it works.

    It’s an improvement to when they required you to use this special software that only worked with internet explorer … now it’s only 10 years behind the times.

  2. The worst aspects of Private PAIR EFS-Web are the following:

    (1) knowing what is the latest version of Java EFS-Web will currently accept. As a user of Private PAIR, I generally get notification about what version of Java is currently usable with EFS-web;

    (2) utter frustration in being able to check status of cases through Private PAIR using common web browsers such as Google Chrome and IE. Trying to upload my .epf certificate using these browsers is usually more “miss” than “hit,” so much so that I’ve had to install Mozilla Firefox to guarantee my access to Private PAIR.

  3. Pingback: Does this check box ever actually work? - Ant-like Persistence

Leave a comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.