The number of bugs in Firefox and the Firefox Java plugin that affect the openinfocard id selector increased in the last days/weeks. Not funny. - eval(..., scope) regression - javascript instanceof not working with Java classes - AccessControlException for java based Firefox extensions - javascript array constructor not working with Java classes - window.java is sometimes defined but sometimes not Sun says they can not fix the java plugin for java 6 update 10... Aaargh. Maybe it is time to build

Have you ever wondered how Firefox finds the Java plugin on Windows systems? The reason you might start to wonder is that Firefox finds the plugin even when you installed Firefox after you had installed Java... The trick is that Firefox - as long as you don't configure it not to do this - scans the Windows Registry. If you experience problems with the new NPRUNTIME version of the Java plugin you can disable it like shown in the picture. This solves problems Java based plugins like the openinfocard

There are currently issues with java in Firefox3 that prevent the openinfocard id selector to function reliably. For the time beeing: If you want to use/try the openinfocard id selector then please use Firefox 2.0.0.16 . Mozilla and Sun are changing the way java works in Firefox and this seems to be problematic. While I could work around some issues, there is no workaround for others. Using 6u10 makes things worse. The current problems break all java extensions in Firefox3 that use the jar file loading

The early betas of Firefox3 crashed when the openinfocard identity selector was loaded. The current beta and the one before do not crash, but don't work. InternalError: Unable to convert JavaScript value file:/C:/Dokumente%20und%20Einstellungen/Nennker.Axel/Anwendungsdaten/Mozilla/Firefox/Profiles/kb7ofbop.default/extensions/ %7B211DBAEA-CE99-11DA-8254-96BEC52F3316%7D/components/firefoxClassLoader.jar to Java value of type java.net.URL[] Yesterday I retrieved the latest Firefox3 code from CVS and

The openinfocard id selector now works with Firefox3 . The bug in Firefox3 is not fixed but circumvented. Firefox3 treats arrays of java objects differently than before. In a javascript script the call "java_method([aElement])" formerly worked but now it fails. It has to be replaced with var urlArray = java.lang.reflect.Array.newInstance(java.net.URL, 1); urlArray[0] = aElement; // aElement beeing a java.net.URL java_method(urlArray); Please download the latest version in the openinfocard download

I have no shame... and must tell that a first step in realizing the openinfocard selector as a Firefox plugin instead of an extension was achieved today. A Firefox plugin is probably the correct way to handle HTML <object type="application/x-informationcard" >...</object> inside Firefox. When I implemented the certificate chain validation I had to build my own Firefox browser from sources because I needed an API that is not in the Gecko SDK but in the Firefox source code. Now I had everything

Projects seem to need a logo . I hope that this quick (non-art) work finds some supporters. Or should should it be this one?

This is cool. I was thinking of giving this a try myself. An identity selector that speaks SAML instead of WS-*. This should not be that complicated when you mix the openinfocard selector with a java SAML library. Add ingredients, shake well, stir, ready. I am wondering if they took the photo shot before or after they began this project.

There is currently a discussion how and if a browser should indicate the presence of installed id selectors. I am against "polluting" the user-agent string. Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; WOW64; SLCC1; .NET CLR 2.0.50727; .NET CLR 3.0.04506) This indicates only that .NET3 is installed, it does not tell the relying party whether CardSpace is active or disabled. I prefer that the id selector adds a HTTP header e.g. "X-ID-Selector" to the HTTP requests. This is easy to implement;

A prototype for exchange of dynamic information