It is astonishing that even now, in August of 2015, despite many warnings and requests from users over the span of several years, USPTO has not scrapped its Java applet. By this I mean the Entrust Java applet which USPTO forces customers to use to authenticate their logins at Private PAIR and EFS-Web. The most recent reminder of all of this is USPTO’s oddly worded “Third Notice”, an email alert on August 18, 2015 from the USPTO warning customers that time is running out for users of Chrome browsers. In September of 2015 (that is, during the next month) Chrome will stop supporting Java, meaning that users of Chrome will no longer be able to log in at Private PAIR or EFS-Web.
Until now I had sort of thought of Chrome as a relative newcomer among web browsers, and I had sort of assumed that most people still use Firefox and Microsoft Internet Exploder. Which got me wondering, how many USPTO customers use Chrome anyway?
USPTO’s not saying how many of its customers use Chrome. But I’d guess that the mix of visitors to my firm’s web site (www.oppedahl.com) is a fairly good predictor of the mix of visitors to the USPTO’s web site. So today for the first time in many months, I took at look at the web browser statistics for our web site, and I was a bit surprised by what I saw. It turns out (see graph above) that 49% of the visitors to our web site use Chrome.
This shows what big trouble USPTO is in. Even if the percentage of Chome users among USPTO’s customers is not as high as our 49%, it is surely substantial. And all of these customers will run into trouble in September when they find they can no longer log in at Private PAIR or EFS-Web.
Did Google ambush the USPTO about this change to Chrome? No. Google announced two years ago (in 2013) that Chrome would stop supporting Java in 2015.
And it is not as though Chrome is the only browser to stop supporting Java. The newly released Microsoft Windows 10 has as its native web browser a browser called Edge that has never supported Java and presumably never will.
I have warned the USPTO about this problem many times over the past several years, most recently in this blog in May of 2014 (see A reminder that USPTO needs to scrap the Entrust java applet for PAIR and EFS-Web posted May 29, 2014). But it’s not just me. Others have also discussed USPTO’s dependency upon Java for access to Private PAIR and EFS-Web, for example in 2012 (Intelproplaw forum, Kaplan IP law blog) and in 2013 (PatentlyO). USPTO’s own Ideascale system (a sort of online bulletin board in which USPTO solicits suggestions from customers) shows that customers warned USPTO about this problem some six months ago.
It is only a matter of time, of course, before the remaining browsers with meaningful market share (Internet Exploder, Firefox, and Safari) will likewise drop support for Java, due to the security and stability risks that it presents.
What is USPTO’s response to this imminent demise of Java? You might think that USPTO would pick a new authentication mechanism and announce a date by which it would be rolled out. Instead, the present public position of USPTO as communicated on USPTO’s web site is:
- USPTO is “closely monitoring for any changes”
- USPTO is “committed to keep the IP Community informed accordingly”
- USPTO is “investigating if there are possible strategies to mitigate the impact”
- USPTO is “working on a longer term plan”
That’s just not good enough. “Closely monitoring” and “keeping the IP Community informed” is not good enough. There is no need to “investigate” to see if there are “possible strategies to mitigate the impact”. Of course there are possible strategies, like scrapping the Java applet. And it’s not good enough to “work on a longer term plan”. What is urgently needed is a present-day plan.