http://www.google.de/search?q=cardspace+site%3Amicrosoft.de yields:
Not good! It seems that the German Microsoft site is not searched by Google. Strange.
Ahh. Searching for German language content on microsoft.com yields results...
Still...
Searching for Cardspace at search.microsoft.com results in an interesting suggestion: "Meinten Sie vielleicht: cards pace" (did you mean 'cards pace'). It seems that search.microsoft.com does not know Microsoft products.
Tuesday, May 26, 2009
Your search - cardspace site:microsoft.de - did not match any documents.
Posted by
Unknown
at
3:13 PM
0
comments
Labels: CardSpace, german language, google, Microsoft, search
Monday, May 25, 2009
J2SE 5.0 is in its Java Technology End of Life (EOL) transition period
"J2SE 5.0 is in its Java Technology End of Life (EOL) transition period. The EOL transition period began April 8th, 2008 and will complete October 30th, 2009, when J2SE 5.0 will have reached its End of Service Life (EOSL)."
While playing around with some SUN developement kit and trying to build the samples I got the error message that the version of the class files do not match. One gets this error message when some jar file was generated with another version of Java... Some time ago I deinstalled all old versions of Java from my computer keeping only the Java 6u13 JDK. It turns out that I need Java 5 to build the samples. Not good.
I downloaded java 5 and succeeded to build the samples... But anyway SUN should see to it that this does NOT happen. Especially with its own SDKs.
I already deinstalled java 5 again, but will keep the installer on disk for future incidents like this.
Migrate to java6 now!
Another pain point: What about J2ME? Are there any plans to update this java-1.3-ish language to java6? Android has java 6 but that is another league.
Posted by
Unknown
at
3:16 PM
0
comments
Labels: Android, java, sun, Sun Microsystems
Tuesday, May 19, 2009
who is jvsmith.pip.verisignlabs.com
Just wanted to try Facebook as an OpenID consumer. So I undusted that Facebook account and added my verisignlabs openid ignisvulpis.pip.verisignlabs.com to my profile.
When I come back from verisignlabs Facebook presents my updated profile.
My openid is presented to me as: jvsmith.pip.verisignlabs.com which points to the correct openid. What is going on here?
I quick search reveals that others have the same problem... Strange.
Posted by
Unknown
at
6:58 PM
1 comments
Labels: facebook jvsmith, OpenId
developer garden

Normally I do not blog about my employer but this time I would like to make an exception.
Deutsche Telekom launched its developer platform called "Developer Garden". This is great. Currently you can send SMS, start telephone calls and resolve IP addresses to locations. Nice. I wish I had time to start another opensource project for this that uses Information Cards and the IP Location service. Or my employer would give me the time to do this...
Two things come to mind.
- create an STS that issues IP location cards. When the user uses this card at a relying party the IP location STS resolves the IP Location and puts the location information into a SAML assertion. Easy.
- create a Firefox 3.x (x>0) location provider that uses the IP location service in the browser. I guess that raises some location provider and browser location GUI issues. Doable.
Although not everything must be done with an Information Card. Providing location information through a card is not widely accepted in the Internet user population ;-)
Anyway. I do believe that relying parties want location information and that Information Cards are a good way to provide claims about a user with the user's consent.
This again raises the issue that we need security tokens that hold claims values assured by multiple sources (IdPs). But maybe this does not really matter. The user does not know about all the underlying technology and he should not need to care about it. I am thinking about a UI where the cards (and the claims) are presented to the user, who then drags the cards or only some claims from several cards to the relying party. The selector then fetches the security tokens from the multiple IdPs and sends the multiple security tokens to the relying party.
How does the selector know about where to post what claims? Through XRD.
Posted by
Unknown
at
9:36 AM
0
comments
Monday, May 18, 2009
Internet Identity Workshop & openinfocard
The Internet Identity Workshop seems to inspire me to work more on the openinfocard selector again. I just uploaded a new version. Drag and Drop of Information Cards works again. You can open the sidebar using shift-alt-ctrl-i and then drag one of your cards to the main window (relying party).
The selector then opens and the dragged card is choosen. You just need to hit the "send" button or select some optional claims first.
You should look at the details of this particular relying party (http://pamelaproject.com/wptest091/). Pamela implemented the use of XRD/S for information cards for her wordpress plugin. If you add something like
<meta http-equiv="X-XRDS-Location" content="http://pamelaproject.com/wptest091/?xrds"/>
to your site and you use openinfocard then you can use Information Cards without the "object"-HTMLElement.
Posted by
Unknown
at
12:07 PM
0
comments
Labels: iiw2009a, iiw8, openinfocard
Tuesday, May 05, 2009
ICF D-A-CH Chapter @ EIC
Today at the European Identity Conference we had a workshop on forming a local chapter of the Information Card Foundation. We intend this to be a local chapter for Switzerland, Austria and Germany. We want to provide helpful information about Information Cards in the German language, we want to be a neutral body and an open organization, we want to organize and participate in events and workshops, we want to identify local requirements and local legislation related to Information Card Applications and we want to solve or to help solve challenges related to those local requirements and restrictions.
In our first workshop today we had many interesting presentations from very different companies and organizations. I won't repeat them here other then to note that probably all aspects of the Identity Metasystem were covered. That kind of surprised me, but it was a good surprise because it reminded me that there are more aspects to this other than the projects I work on. I thought that my openinfocard project and the Cardspace4Firefox project cover the selector part, that my divers work projects cover consumer, enterprise and mobile devices parts of the systems and the interoperability and standards aspects and that this is most of the "world" but of this of course not true. I was remembered that there is even more than this already huge field. That is good.
Posted by
Unknown
at
2:57 PM
0
comments
Labels: CardSpace4Firefox, eic, eic2009, icf, local chapter, openinfocard
Thursday, April 30, 2009
openinfocard new version
I just uploaded a new version of the openinfocard selector to http://code.google.com/p/openinfocard/downloads/list.
Please give it a try.
The changes are mainly internal but huge and important. After over a year of despair caused by several java plugin2 hiccups and a lingering "stale reference to a java vm"-error I think that I now have improved the code so that development of new features makes much more sense then before. I had the feeling that SUN and Mozilla are pulling away the ground under my feet, but now I think this period is over.
Some improvements are "visible" when you try the selector with "complicated" IdP's. I improved the metadata parsing through hefty use of E4X. The OSIS endpoints do not fall into this category but if you test this openinfocard version e.g. with a Geneva server you might see what I mean. We have set up Geneva servers in our lab and openinfocard immediately failed. I fixed this; although I am sure that there are WS-* variants that still cause the selector to flip.
BTW: By fixing some of these faults I "improved" the internal cardstore format. This causes old cardstores to become unusable. Sorry, please remove the cards from your current cardstore and reimport them. There is no automatic conversion...
Jave6 u12 or newer is now a requirement. I have only tested it on Windows XP SP3 32bit but I am quite confident that this selector runs everywhere where Firefox 3 and java6 is available.
Next steps:
- code cleanup. Throw away now unused code.
- XRDS support for X-XRDS-Location meta tag (nearly ready)
- phone selector integration
Posted by
Unknown
at
9:30 PM
3
comments
Labels: e4x, geneva, openinfocard, osis
Friday, April 24, 2009
user-agent pollution .NET CLR 3.5.30729
Don't know when this started but currently the Firefox user-agent string is polluted by new a new addition "(.NET CLR 3.5.30729)".
Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.0.9) Gecko/2009040821 Firefox/3.0.9 (.NET CLR 3.5.30729)
Maybe the new add-on "Microsoft .NET Framework Assistant" is to blame.
But although I disabled it the user-agent string was not reverted to normal.
Who gave Microsoft the right to blurt about the fact that .NET3.5 is installed on my computer?! Well, others are not better: If the Azigo Selector is installed then it adds itself to the user-agent string too.
Maybe SUN should add the installed Java version and whether OpenOffice is installed, and Adobe the installed Acrobat Reader version and the Flash version, and Apple the Quicktime and iTunes version and ...
Posted by
Unknown
at
2:45 AM
0
comments
Labels: .net3.5, Azigo, identity selector, Microsoft
Wednesday, April 22, 2009
Oracle Identitymanagement 20% off
the book price as seen in the RSA conference bookstore today.
I am sure this has nothing to do with the current aquisition of opensso by Oracle from SUN, or has it?!
Another book of probably only historical value:
contains everything about the past of identitymanagement and authentication on Unix and Windows systems but nothing that is newer than - let's say - three years. What is that good for? A door stopper or a lesson in what does not scale and is inflexible?!
Posted by
Unknown
at
2:24 AM
0
comments
Labels: merger, oracle, sun, Sun Microsystems
Tuesday, April 21, 2009
Kantara, Standards, Open Source Projects
Please pardon the crude title of this post...
On Monday, April 20, 2009 the Kantara Initiative (the server is currently down...) was launched. Although I subscribe to the goals of the initiative I still know too little to make a reasonable decision about it. My feeling is that it is too big. While it certainly helps to have an organisation and most of the legal (IPR, bylaws, etc) stuff is already handled for a new Kantara working group e.g. openFOO/BAR/BAZ I fear that the influence of the big companies might be unhealthy for openFOO. Sure it helps to have supports from experts in e.g. protocol design and standardization to make the openFOO protocol consistent, sound, complete, modular and extensible and everything a protocol or data format should be; but Liberty Alliance, Microsoft, IBM and the other big companies have a tendency to create complex beasts that the normal open source project can not tame.
If some enthusiasts come together, join forces to solve a problem and to make the Internet "suck less" then the outcome is sometimes simple, not modular, not extensible or whatnot but if it solves the problem, well...
A counter example: Yesterday I awoke a 1am (jet lag) and tried the openinfocard selector "against" an IdP that is based on Microsoft Geneva. I imported the Information Card that was issued by that server and boom: openinfocard could not handle it. So I fixed this small problem. (Although this fix will lead to a changed internal format of the openinfocard cardstore and will break existing cardstores. Hm. Sorry). Now I try to use the card and boom: the retrieved WS-Metadata is so complex that the openinfocard selector can not handle it; So I fixed this not so small problem and learned a lot about several of the friendly members of the WS-* family...; and of Mozilla’s E4X implementation. This introduces a new level of complexity to the openinfocard code that surely will lead to trouble in the future.
What does this have to do with Kantara? Well, sure the designers of WS-* are not all members of Kantara but the Liberty Alliance Project has created similar complex specifications (This server is down too; in fact it turns out it is the same server 74.124.198.86).
Now consider you want to implement a cool program on a mobile phone and have to use these standards. Good luck with e.g. ID-WSF and e.g. kxml2. Doable, but this takes probably more than half an hour.
So I am sceptical for small, fast, just-doit openFOO groups.
Posted by
Unknown
at
3:19 PM
1 comments
Labels: Kantara, Open Source Projects, openinfocard, Standards
Monday, April 20, 2009
Oracle will buy SUN
Living in interessting times... (still).
http://www.sun.com/third-party/global/oracle/index.jsp
This raises many questions regarding e.g. mysql etc but most notably I am very curious what this means for opensso and SUN's access manager and ...
This merger will be a hot topic for the identity people here at RSA conference too, I am sure. Can't wait to hear what e.g. Uppili and Pat say.
Posted by
Unknown
at
2:54 PM
0
comments
Labels: identity, identity management, merger, oracle, sun, Sun Microsystems
Friday, April 17, 2009
Waiting for CardSpace Geneva
I wanted this video to loop forever but could not find how this is possible.
Maybe Microsoft should open source CardSpace Geneva; then we could help to bring it into the world.
Posted by
Unknown
at
10:59 PM
0
comments
Labels: CardSpace, cardspace geneva, geneva, Microsoft
Monday, April 06, 2009
xmldap.org is down
I am sorry that xmldap.org is down.
Nulli Secundus, the former employer of Pamela Dingle, hosted xmldap.org until now. A big thank you for that.
Chuck and I have not found an alternative until now.
But I am an ethernal optimist too ;-)
Posted by
Unknown
at
10:24 PM
1 comments
Labels: xmldap, xmldap infocard sts relyingparty
similar people at quillp
Today I tried a new social network quillp that claims to help to establish a new cosmos for me by knowing how I like or not-like books I have read.
They have a subservice that offers a list of books of people similar to me:
I seems I am special and not many readers are similar to me.
Or they don't have their database and algorithms straight.
Well, about every ten click leads to a .NET error like: "table 0 not found".
What I do not like about Quillp: Somebody must explain oauth to them now!
Anyway: I subscribe to the mantra "publish early, publish often" too. And "if your not embarassed by your first version then you published to late".
Quillp has some work to do but I like the idea and happily divulge my bookshelve to them but not my password to other sites.
Posted by
Unknown
at
11:45 AM
1 comments
Labels: data portability, datasharing, oauth, probile, quillp, recommendation, reputation, social network
Wednesday, April 01, 2009
Mozilla weave and Information Cards
Mozilla labs just announced that they released version 0.3 of weave. I think Information Cards should be added to the weave cloud:
And maybe passwords should be stored as Information Cards to leverage THE SELECTOR's anti-phishing capabilities to protect username/password credentials.
Posted by
Unknown
at
11:54 AM
1 comments
Labels: icf, Information Card Foundation, mozilla, openinfocard, openinfocard firefox extension, weave
Tuesday, March 31, 2009
please think of the kittens
While searching what others write about Information Cards I found this older presentation and want to share especially one slide with you: 
If you made OpenID phishing resistant then you have Microsoft CardSpace Geneva?! We need a secure (enough) UI for login and attribute sharing through OpenID, Information Cards and even username/password. I think that cards are a metaphore that users understand and what happens underneath the UI should not really concern the user. I don't want to remember an OpenID or a password, I want to choose a card and what happens under the hood... who cares?! Well, the server vendors care but not the user.
Please join the discussion at the Information Card Foundation!
Posted by
Unknown
at
11:48 AM
2
comments
Labels: CardSpace, geneva, icf, information card, Information Card Foundation, OpenId
Mozilla Add-On Workshop Berlin 2009
Last Saturday I attended the Mozilla Add-On Workshop in Berlin. It happened in the c-base which is a really cool location for this kind of events. Although the rooms are connected like pearls on a string which led to some traffic even during the sessions. Anyway it was a good event and I will go there again when it comes to Berlin again.
Things that impressed me:
- The new video capabilities of Firefox 3.1 are astonishing. You can implement real-time image processing inside the browser to have blue-screen effects or to track people moving in front of the camera or <what-ever-you-can-think-of-on-doing-to-a-bitmap>.
- DOM worker threads bring concurrency to javascript. This can be helpfull if you have a lengthy job to do but I fear that this can have astonishing effects.
- The Mozilla Lab's project weave has a new version. Try it. I think it should be easy to extend sharing bookmarks, open tabs, extension from machine to machine to Information Cards and Information Card stores too.
Things that need more work:
- Mozilla's build system. This is a monster.
- I tried to build Firefox with Windows SDK 2008 and the .NET 3.5 framework -> no fun
- crypto support in Mozilla is poor. I need xmldsig, xmlsec and some "basic" digest and crypto (RSA-OAEP-MGF1P) in extensions.
- Java access from javascript extensions seem to go down the drain unless mozilla and sun do something.
Posted by
Unknown
at
10:25 AM
1 comments
Labels: Firefox extension, firefox3, information card, java firefox plugin, maowberlin09, video, weave
Wednesday, March 18, 2009
RSA 2009 US Personal Schedule for Axel Nennker
| RSA 2009 US Personal Schedule for: Axel Nennker |
| Monday | ||
| SEM-002 | Harnessing the Power of Digital Identity: 2009 and the Promising Road Ahead | |
| Tuesday | ||
| KEY-101 | A Common Call: Architecting a New Information Security Landscape | |
| KEY-102 | The New Security Agenda: Changing the Game | |
| KEY-103 | Moving Towards 'End to End Trust': A Collaborative Effort | |
| KEY-104 | The Cryptographers' Panel | |
| BC-001 | Mobile 2.0 Trends and Threats | |
| BC-002 | The Next Generation of Security - Cyber Security | |
| ESS-105 | Fostering Collaboration and Opportunities in Identity Management | |
| STAR-106 | Using Claims to Simplify and Secure User Access to Applications and Services | |
| ESS-107 | Information Cards What User-Centric Computing Can Do for Your Enterprise | |
| ESS-108 | Building Authorization Into The Enterprise Identity Metasystem | |
| Wednesday | ||
| KEY-206 | Collaborate with Confidence | |
| BC-014 | A Pragmatic Approach to Building Identity Management for the Enterprise | |
| Thursday | ||
| PROF-301 | Professionalizing the Security of Software Development | |
| P2P-302A | Identity and Privacy Models | |
| P2P-303B | Claims-Based Identity - What is the Business Case? | |
| NET-304 | Mobile Operator's Perspective on Security | |
| P2P-305B | Raising the Bar on Authentication | |
| KEY-307 | The Transformation of Identity and Access Management | |
| Friday | ||
| 11:00-16:30 | Information Card Foundation Directors Meeting | |
Posted by
Unknown
at
11:09 AM
0
comments
Labels: identity, Information Card Foundation, rsa, rsa2009
Tuesday, March 10, 2009
Car Re-Registration with Information Cards and German eID by Fraunhofer Fokus
Fraunhofer Fokus demoed a cool scenario where a user re-registers his car using the new German eId and Microsoft CarsSpaceCardspace. What I exspecially liked that the slides show Firefox and the openinfocard selector installed.

The following is the text from the slide:
Re-registration of a car can prove a real headache. But the Fraunhofer Institute for Open Communication Systems FOKUS in Berlin has joined forces with the Bundesdruckerei to develop the prototype of an electronic automobile re-registration procedure that can be conveniently operated using the home computer.
To use this simple procedure, however, the citizen first requires a safe means of identity in the digital world. He or she requires an electronic identity or ‘e-identity’ which needs to be created, administered and decommissioned.
Across its life cycle the digital identity can be used for a wide variety of different transactions and activities – but always with the aim of proving the identity of the real individual in the virtual world. Users must be able to navigate in the digital world; they must reveal certain information about themselves – but not too much and certainly not to everybody. At the same time increasingly pervasive networking means that previously separate islands of identity have now to interact and cooperate.
In the ‘Re-registration of an Vehicle’ scenario the car owner can use an electronic ID card as a means of identification of the type that will come into use in Germany in 2010. Using this card she logs onto a user-centric service – the scenario uses Windows’ CardSpace – which issues her with a ‘digital card’ or Information Card which she can use via an identity provider to safely authenticate herself on an vehicle portal. Using an electronic vehicle registration certificate – which could also become widely available in future – the car registration office can then read off the key data about the car via the internet and store the data that has been changed.
The citizen then transfers the revised data to a future digital license tag.
Please contact Jens Fromm from Fraunhofer Fokus for more information.
Posted by
Unknown
at
10:05 AM
0
comments
Labels: CardSpace, eID, Fraunhofer Fokus, openinfocard, openinfocard firefox extension
Thursday, February 26, 2009
Public Review of Identity Metasystem Interoperability Version 1.0
OASIS has sent the following information out today:
Identity Metasystem Interoperability Version 1.0
Introduction:
The Identity Metasystem Interoperability specification prescribes a subset of the mechanisms defined in WS-Trust 1.2, WS-Trust 1.3, WS-SecurityPolicy 1.1, WS-SecurityPolicy 1.2, and WS-MetadataExchange to facilitate the integration of Digital Identity into an interoperable token issuance and consumption framework using the Information Card Model. It documents the Web interfaces utilized by browsers and Web applications that utilize the Information Card Model. Finally, it extends WS-Addressing's endpoint reference by providing identity information about the endpoint that can be verified through a variety of security means, such as https or the wealth of WS-Security specifications.
This profile constrains the schema elements/extensions used by the Information Card Model, and behaviors for conforming Relying Parties, Identity Providers, and Identity Selectors.
The public review starts today, 26 February 2009, and ends 27 April 2009. This is an open invitation to comment. We strongly encourage feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of OASIS work. Please feel free to distribute this announcement within your organization and to other appropriate mail lists.
More non-normative information about the specification and the technical committee may be found at the public home page of the TC at http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=imi. Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be located via the button marked "Send A Comment" at the top of that page, or directly at http://www.oasis-open.org/committees/comments/index.php?wg_abbrev=imi.
Submitted comments (for this work as well as other works of that TC) are publicly archived and can be viewed at http://lists.oasis-open.org/archives/imi-comment/. All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the
feedback you provide carries the same obligations at least as the obligations of the TC members.
The specification document and related files are available here:
Editable Source:
http://docs.oasis-open.org/imi/identity/v1.0/cd/identity-1.0-spec-cd-02.doc
PDF:
http://docs.oasis-open.org/imi/identity/v1.0/cd/identity-1.0-spec-cd-02.pdf
HTML:
http://docs.oasis-open.org/imi/identity/v1.0/cd/identity-1.0-spec-cd-02.html
Schema:
http://docs.oasis-open.org/imi/identity/v1.0/cd/identity-1.0-cd-02.xsd
http://docs.oasis-open.org/imi/identity/v1.0/cd/addr-identity-1.0-cd-02.xsd
http://docs.oasis-open.org/imi/identity/v1.0/cd/claims-1.0-cd-02.xsd
OASIS and the IMI TC welcome your comments.
I hope that we will have an official OASIS standard for Information Cards soon.
Well, musing about "soon". I am wondering how long these things take. I joined Chuck Mortimore and the Openinfocard project in August 2006. We had the first open source Information Card relying party and the first open source IdP, both written in Java and Java Server Pages. Then of course the first open source card selector as an Firefox extension, written in javascript, XUL and Java.
Time is flying when you are having fun.
Posted by
Unknown
at
8:42 AM
0
comments
Labels: information card, OASIS, openifnocard
Wednesday, February 04, 2009
java 6 update 12 for openinfocard

Java 6 update 12 has been released. Please install this update because it contains a fix (6745455) especially for Firefox extensions that use java like the openinfocard id selector. openinfocard users on MacOS still have to disable the plugin2 and use the dying OJI plugin (or stay with Firefox 2...); although that is not really satisfying... I hope that Apple will leap ahead soon from java 1.6u7 to 1.6u12.
Thank you SUN for fixing this.
Posted by
Unknown
at
9:16 AM
0
comments
Labels: java, java firefox plugin, openinfocard, sun
Sunday, January 25, 2009
Backward Compatibility. Java, Mozilla, Sun, IBM, Microsoft
About a week ago there were press articles about SAP paying SUN Microsystem to support SAP customers with stoneage java 1.4 users/systems.
Unfortunately there is nobody who wants to own and support the stoneage OJI project that puts java support into Firefox. The new way to support java is provided through the NSAPI plugin interface and the new thing is called "plugin2". Unfortunately (again) SUN forgot - or never knew - that Firefox extensions have - if they want - all the rights of the Firefox user. SUN implemented plugin2 having java applets in mind. Firefox extension that use java were forgotten.
But Sun is very helpful to ease the pain and supports me - thanks Kenneth - in rewriting the java classloading stuff from OJI to plugin2. But (again) you need java 6 update 12 or newer for this to work. This version of java has a patch for plugin2 that gives Firefox extensions the necessary priveledges.
So currently there are two options for openinfocard users: either disable plugin2 as I discribed in previous posts or install java6u12ea.
When Mozilla stops support for OJI then there is only the option to install a current version of java. I guess that Firefox 3.2 will not have OJI inside.
This reminds of an email thread/t on the higgins-dev mailing list. Where most developers wished for java 5 in higgins but IBM's shogun ordered his men to commit harakiri should they become traitors to java 1.4. Well, I am exaggerating...
I guess that IBM does not want to pay SU... - Hm, IBM has its own java - IBM to migrate customers stoneage IBM systems to a better world?!
Other memories bubble up: Did you remember the news that Microsoft CardSpace was downgraded to run on FAT file systems?
Well, well, well. I am happy that openinfocard is provided AS-IS.
I will do my best to support all versions of Firefox on all platforms, but my resources are limited. So we all should be happy if we can always work with the latest and greatest software. Happy downloading. Enjoy.
Posted by
Unknown
at
11:11 PM
0
comments
Labels: CardSpace, compatibility, Microsoft, openinfocard, sun
3500 New Jobs at Deutsche Telekom
Today I read about SUN Microsystem laying off 1500 people. Last week I read about Microsoft laying off 5000 people.
Time for some good news: Deutsche Telekom says it might offer 3500 new jobs.
Deutsche Telekom is planning up to 3,500 new jobs in Germany in 2009, dependent on the economic development in its individual business segments, CHRO Thomas Sattelberger announced today in Bonn.
Posted by
Unknown
at
2:06 PM
1 comments
Labels: Deutsche Telekom, jobs, Microsoft, Sun Microsystems
Wednesday, January 21, 2009
SUN ONLINE ACCOUNT Identity Management Stinks
I am currently testing the openinfocard identity selector with Firefox 3.1 beta 2.
Well, this does not look good.
The color/layout of the xmldap relyingparty is "different" to the Firefox 3.0.5 look.
The fonts look strange.
The layout of the claims in the openinfocard CardManager window is completely disastrous.
The generation of self-issued security tokens through Java does not work. No error message - just nothing happening. This is what I like.
As a good member of the Sun / Mozilla developer community I searched SUN's bug database for something related.
The bug (6745455) "Firefox extensions using Java don't work with new Java Plug-In" looks interesting. BUT you need an account to see this! What is this? Still quite cool at this point. So I tried my SunSolve account to login but the contract seems to be expired. Next I tried my SUN Developer Network account but still no access to this bug. Well SUN Online is offering me to register for a SUN ONLINE ACCOUNT. Pseudonyms are cheap. Tried this, verified my email address, relogin, BUT still no access to this bug.
This stinks!
Now I have three SUN accounts. The first two because years ago SUN was not able to merge the two and after SUN forced me to create the second after they tried to consolidate their user databases (but failed). What's more: I can not find the button/link to terminate/delete the new account. Super.
So much for that. I will pester my SUN contact with the java plugin2 error now.
Thank you SUN for wasting my time.
The bug:
if you enter
"Components.classes["@mozilla.org/oji/jvm-mgr;1"].getService(Components.interfaces.nsIJVMManager)"
into the command line of the Firefox console then Firefox 3.0.5 returns
"[xpconnect wrapped nsIJVMManager]" while Firefox 3.1 beta 2 returns "Fehler: Component returned failure code: 0x80570018 (NS_ERROR_XPC_BAD_IID) [nsIJSCID.getService]
Quelldatei: javascript:%20Components.classes["@mozilla.org/oji/jvm-mgr;1"].getService(Components.interfaces.nsIJVMManager)
Zeile: 1". My guess is that this is an easy test for the bug that causes openinfocard to stop working with FF3.1b2. Maybe this is easy to fix in the openinfocard extension. I guess that OJI support is dying, but what is the new call to get the Java console?
Posted by
Unknown
at
3:34 PM
0
comments
Labels: bug, identity management, openinfocard, sun
Tuesday, January 20, 2009
openinfocard codeswarm
A codeswarm video of code repository checkins for the openinfocard project.
Interessting for me are the times of much activity and the times of little activity. Maybe I can provide subtitles like "OSIS Barcelona Interop". I guess that those events triggered many code changes. This is probably a good chance to remind everybody to start testing for the next interop which ends at RSA 2009.
If you want to create your own codeswarm video, it is easy. The repository must understand SVN but that is probably the major obstacle some project might face.
Posted by
Unknown
at
10:02 PM
0
comments
Labels: codeswarm, information card, openinfocard, osis, rsa
DIDW 2009
This is the first reference to this year's Digital ID World:
I could not find it on CSO's website. The link there currently points to the 2008 event. Does somebody know more or is it cancelled?
To see the full epic movie from which I captured the picture please visit Ping Identity's blog.
Posted by
Unknown
at
3:49 PM
0
comments
Labels: DIDW, pingidentity, SSO
Saturday, January 17, 2009
Frightening? Geolocation
Two years ago I was working on VoIP emergency calls and how to determine the location of the caller. With VoIP the problem is equal to determine the location of an IP connected device. The security and privacy issues with this are "tricky".
Last week I played with the new W3C geolocation API draft and Mozilla's GEODE Firefox extension.
Today I restarted my "playground"-laptop and Firefox was restarted and Aza Raskin's geolocation demo site was displayed. I was baffled that the location displayed was my old(!) home address. But then I thought: "Somebody connected my WLAN-router to my old address" and that is why this location gets displayed. Now, three hours later, I wanted to power-off the laptop but reloaded the demo site. INTERESTINGLY, now my new and correct address is displayed. That is frightening. I am now living outside Berlin "in the woods" between Berlin and Potsam but nevertheless there is a connection between my WLAN or my neighbors WLAN to this location. I am not sure whether I want my location resolved by a server in ... whereever. Well, I don't have to use the GEODE extension and the loki.dll that is used by GEODE. Do I trust Skyhook who build loki? Hm, although my G1 and the iPhone too might use WLAN-location but I prefer GPS. With GPS my WLAN environment is not send around the world.
Nevertheless I might write a geolocation provider for Firefox 3.1 which has W3C geolocation support build-in. Maybe that extension (IdP) will use geolocation Information Cards to choose which claims (exact-location, neighborhood, city, ...) to reveal to the RP.
Posted by
Unknown
at
10:48 PM
0
comments
Labels: G1, geolocation, GPS, iPhone CardSpace "Bandit Project" openinfocard, WLAN
Thursday, January 15, 2009
Playing Around with Microsoft Tags
Some see visual tags as a danger to NFC's breakthrough... Well, maybe; but only for a subset of NFC use cases.
Reason enough to try it out. So I created a tag at Microsoft. Had to login with liveid/password. Wondering when Information Card support will be there at liveid... And here it is: 
Now we need the software from gettag.mobi. Hmm. Android not available yet for my G1. Symbian S60 is there but my S60 phones (E60 and E61) don't have a camera. My 6131-NFC (well) has a camera. I downloaded the j2me-unlocked program and installed it on the 6131 using Nokia's PC Suite's application installer. I was able to start the tagreader application and it successfuly decoded the tag on this page... but the phone has not valid internet connection settings...
Hm. Enough playing around. I might try it again when an Android G1 tagreader is available.
BTW: the tag points to the openinfocard download area. Well, to be more exact: it points to a Microsoft server that points to the openinfocard download area. So Microsoft is a man-in-the-middle. Do I want that? No.
Posted by
Unknown
at
2:29 PM
0
comments
Labels: Android, j2me, Microsoft tags, nfc, Symbian
Thursday, January 08, 2009
openinfocard is now on addons.mozilla.org
I uploaded the current version of the openinfocard firefox extension to addons.mozilla.org. It is there in the experimental section. Sorry you have to have a mozilla account to download it from there. The future current versions will be available at the project's code repository as long as the extension is not in the section of released extensions.
Enjoy.
Posted by
Unknown
at
10:53 PM
2
comments
Labels: addon, extension, firefox, mozilla, openinfocard
Tuesday, December 30, 2008
Firefox XRD Extension II
I just uploaded a new version of the XRDS extension for Firefox and a version of the openinfocard extension that uses it.
When the extension xrds_pageinfo.xpi is installed then the openinfocard extension shows the list of cards that where used at this site. Hm, to be more precise: The list of Information Cards is shown of which a record of usage is stored in the cardstore. If you use the new "delete privacy data" feature of the openinfocard extension then no card usage is shown.


Also available in other languages than German.
have fun
Axel
Posted by
Unknown
at
10:48 PM
0
comments
Labels: Firefox extension, openinfocard, xrds
Friday, December 05, 2008
Firefox XRD Extension
Even so progress is slow sometimes...
Sometimes things actually move forward.
Based on the discussion at IIW and the former posts I started to write an extension for Firefox that allows users to see the XRDS provided by a site.
I see this as a further step to get IDentity In the Browser. But not only "openid in the browser" but much more.
First let's see how this looks.
Well. All my new Firefox extension currently does for the user is to show just that xml. Click on the favicon of the site and you will see something like this:
But there is more to come and there is more under the hood. The extension implements a component in javascript that allows other extensions to access the discovered XRDS and add/remove handler for services defined in the XRDS.
The current interface definition for the component is:
[function, scriptable, uuid(13e630b8-3f41-456b-ae26-c30b201c8f99)]
interface IXrdsServiceHandler : nsISupports
{
boolean handle(in nsIDOMElement service, in nsIDOMDocument doc);
};
[scriptable, uuid(DDD9BC02-D964-4bd5-B5BC-943E483C6C57)]
interface IXrdsComponent : nsISupports
{
void addServiceHandler(in ACString xrdsServiceType, in IXrdsServiceHandler aXrdsServiceHandler);
void removeServiceHandler(in ACString xrdsServiceType, in IXrdsServiceHandler aXrdsServiceHandler);
IXrdsServiceHandler iterator(in ACString xrdsServiceType);
long getHandlerCount(in ACString xrdsServiceType);
IXrdsServiceHandler getHandlerByIndex(in ACString xrdsServiceType, in long index);
void addXrdsForSite(in ACString site, in AUTF8String xrds);
AUTF8String getXrdsForSite(in ACString site);
};
This interface definition will change. But after I have integrated this into the openinfocard identity selector and after feedback from the other XRD-enthusiasts and perhaps integration into "openid in the browser" I expect something stable no so far away.
What next?
- provide some useful GUI
- it should be possible to click on a button and this will retrieve the privacy policy of the relying party or openid consumer if that service is defined by the XRDS.
- click and the Information Card selector starts and your chosen claims will be send to the RP.
- click and your openid attributes are retrieved and provided (without stealable credentials being involved).
- click and the browser opens the page where you can edit your data.
- click and the browser opens the page that lets you terminate the relation to this site.
- click and you can present your voucher.
- click and you are a new customer with verified claims.
- integrate with openinfocard id selector
- integrate with IDIB
- standardize all this
- standardize service types
- standardize this usage of XRDS for relying parties, openid consumers, webshops, whatever
- There are many open questions. Implementing this and defining service types etc is fruitless if there is no (industry) standard.
I hope that I can work in the OASIS TC(s) relevant to this. Currently it looks like joining is next to impossible. I spare you the details.
I would like to end with something positive... So please find the Firefox extension here. Please send suggestions to
Happy Xrd-ing. -Axel
Posted by
Unknown
at
8:29 PM
2
comments
Labels: IDIB, OpenId, openifnocard, openinfocard firefox extension, xrds
Tuesday, December 02, 2008
Pamela Dingle Speaks
Join veteran Experts Conference speaker Pam Dingle as she shares tips and tricks on how to achieve 'enlightened bottom-up' Identity Management. Pam believes that, as long as you start with a few simple overarching strategic principles, identity management can be 90% tactical. Pamela will use her professional IdM experience to show how the right selection of point solutions in the enterprise can make a world of difference, providing strategic agility to the business while pre-emptively reducing complexity for the future. Look for ILM, Federation and CardSpace to be key technology players in this talk, complete with real-life examples that tie it all together.
The Experts Conference, March 22-25, 2009 in Las Vegas, NV presents her talk "The Survivalists Guide to Identity Management".
Posted by
Unknown
at
8:40 PM
1 comments
Labels: conference, identity management
Tuesday, November 25, 2008
java again

I got a new computer and tried the openinfocard id selector with it; but Boom the Java code did not run. Hm, I forgot to install a new version. Preinstalled was some Java 1.4 version... I installed Java 1.6 update 10 and tried again, but again it failed. Ahh, the new java plugin for Firefox hit me again.
Error calling method on NPObject! [plugin exception: java.security.AccessControlException: access denied (java.security.SecurityPermission getPolicy)]
I had to set HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Plug-in\1.6.0_10\UseNewJavaPlugin from 1 to 0 to disable the new plugin.
After that the openinfocard selector worked again.
Sun promised to fix this in Java 1.6 update 12 but there is no early access version available...
Another bug in the new plugin is that it does not implement the instanceof operator for Java objects.
Kenneth from Sun suggested a workaround: Have to change
if (!(bootstrapClassLoader instanceof java.net.URLClassLoader)) {
to
if (!(bootstrapClassLoader.getClass().isInstance(java.lang.Class.forName("java.net.URLClassLoader")))) {
For this bug there is not even a promise to fix it... Well, thank you SUN for making my life interesting; NOT.
Posted by
Unknown
at
4:40 PM
2
comments
Labels: java, java firefox plugin, javascript, plugin2
Friday, November 21, 2008
Information Cards for Google Apps
Information Cards are an industry standard that enable people to maintain a set of personal digital identities.
Information Cards are like cards in your wallet. Each one defines a relationship between you -the cardholder- and the card issuer -the identity provider. They provide a way to transfer claims/attributes from the identity provider to a relyingparty. Information Card selectors are available for all major operating systems and major browsers. To learn more about Information Cards please visit the Information Card Foundation.
Having provided support for "SAML Single Sign-On (SSO) Service for Google Apps" not so long ago Google is now proud to present support for Information Cards for Google Apps.
The step from "SAML Single Sign-On (SSO) Service for Google Apps" to Information Card support is actually quite small. This is due to the fact that all Information Card selectors are token agnostic that is: They don't care which type of token is transfered from the identity provider to the relying party. Therefore we choose to use SAML assertions that are used in "SAML Single Sign-On (SSO) Service for Google Apps" too.
Security Assertion Markup Language (SAML) is an XML standard that allows secure web domains to exchange user authentication and authorization data. Using SAML, an online service provider can contact a separate online identity provider to authenticate users who are trying to access secure content.
Google Apps offers an Information Card based claims transfer that provides partner companies with full control over the authorization and authentication of hosted user accounts that can access web-based applications like Gmail or Google Calendar. Using the Information Card model, Google acts as the relying party and provides services such as Gmail and Start Pages. Google partners act as identity providers and control credentials and other information (claims/attributes) used to identify, authenticate and authorize users for web applications that Google hosts. Google wants to point out that it is hard to overestimate the security gains for our partners. By using the authentication methods implemented in e.g. Windows Cardspace partners can use Kerberos, X509 and self-issued cards to authenticate the user to the security token server; thereby leveraging existing corporate infrastructure to access Google Apps through this new services.
There are a number of existing open source and commercial identity provider solutions that can help you implement Information Cards with Google Apps.
It is important to note that the SSO solution only applies to web applications. If you want to enable your users to access Google services with desktop clients such as Outlook—for example, Outlook would provide POP access to Gmail—you will still need to provide your users with usable passwords and synchronize those passwords with your internal user database using the Provisioning API.
The Google Apps with Information Card is based the "Identity Selector Interoperability Profile V1.5". Information Cards are supported by several widely known vendors. Visit the Information Card Foundation to learn more.
Understanding Information Card based usage of Google Apps
The following process explains how a user logs into a hosted Google application through a partner-operated identity provider service.
Figure 1: Logging in to Google Apps using Information Cards

This image illustrates the following steps.
- The user attemps to reach a hosted Google application, such as Gmail, Start Pages, or another Google service.
Google presents a page with the purple-i that denotes that Information Cards can be used here. The RelayState parameter containing the encoded URL of the Google application that the user is trying to reach is transferred to the Google ACS as a form parameter. This RelayState parameter not transferred to the partner. Each google app requests at least one claim that is identitcal to the applications base url e.g. "http://calendar.parityapps.com/". - The user clicks the purple-i icon
- The cardselector starts and the user selects her information card e.g. the managed card issued by Parity. The card selectore sends the security token request to the partner
- The partner parses the request and authenticats the user using one of the supported authentication methods Kerberos, X509 certificate, self-issued card or username and password
- Partner generates SAML assertion (security token).
- The browser posts the security token and the other form element's values to the Google ACS
- Google's ACS verifies the SAML response using the partner's public key. If the response is successfully verified, ACS redirects the user to the destination URL.
- The user has been redirected to the destination URL and is logged in to Google Apps.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
I hope to read an anouncement like the fake one above by Google soon ;-)
Posted by
Unknown
at
9:31 PM
0
comments
Labels: CardSpace, google, higgins, information card, Information Card Foundation, information card icon, openinfocard
Tuesday, November 18, 2008
Internet Explorer Mobile 6 Geneva? Not!

Microsoft just announced the new version of Internet Explorer Mobile 6.
The feedback on the PIE blog sounds mostly disappointed.
I guess that the new version still neither has CardSpace support.
I would welcome a mobileCardSpace even if it would have no self-issued card support.
Or maybe we should make the PKCS#5 algorithm in ISIP optional? Self-issued cards are the main reason we don't have mobile selectors.
Sad.
Posted by
Unknown
at
8:58 PM
0
comments
Labels: CardSpace, information card, windows mobile
No XHTML at Information Card Tile Page
Is it only me who finds it anoying that Microsoft over and over again produces example pages that have very very illegal (X)HTML code?
The example page for the Information Card Tile has yet several errors that occure when one uses a framework to create HTML pages that simply does not work well.
One should think that Microsoft's programmers have access to tools that produce valid code?! Or maybe all the Micorsoft tools and frameworks are so that they produce invalid code when you include one page into another?
Bad example. Although I like the Information Card Tile. Even though I would implement it in another way. Some time ago I came up with the same idea but did not implement it because that would have been "not standard". Well, now it seems we witness the birth of a new standard.
I would implement the Information Card Tile รก la microformats by using the class attribute. I would add a special class to the HTML-image tag to denote a tile.
If the RP does not want a tile when no selector is installed then:
Example: <image class="InformationCardTile" src="" id="the-ppid" alt="invisible"/>
If the RP does want an image when no selector is installed then:
Example: <image class="InformationCardTile" src="http://rp/image.png" id="the-ppid" alt="Purple Information Card Icon" onclick="submitForm()"/>
The selector would then overwrite the src-attribute when the card with the PPID "the-ppid" exists and add an onclick-handler that starts the selector or sends the card if the user has chosen to always use this card.
Posted by
Unknown
at
6:23 PM
0
comments
Labels: informationcard, openinfocard, tile
Thursday, November 13, 2008
Equifax Unveils Online Identity Card
ATLANTA, November 13, 2008 - Equifax Inc. (NYSE: EFX) unveiled today the Equifax online identity card or I-Card, with a beta test of a first-of-its-kind digital identity management solution that is designed to make online transactions easier and more secure for both consumers and businesses....
Read the whole story at Parity's website.
Posted by
Unknown
at
10:59 PM
0
comments
Labels: age verification, information card
Wednesday, November 12, 2008
IIW2008b: XRDS for OpenID and Information Cards
We will have a session this morning about XRDS and OpenId and Information Cards.
The IIW2008b wiki has an initial page about this topic.
Please come and let us define something useful.
Posted by
Unknown
at
4:35 PM
0
comments
Labels: iiw2008b, information card, OpenId, openinfocard
Sunday, November 09, 2008
"Big Dog" Wow!
Amazing!
Visit Boston Dynamics for the full story.
Posted by
Unknown
at
4:03 PM
1 comments
Friday, November 07, 2008
Common Browser Add-On
The current version of the openinfocard identity selector now uses the same browser add-on code as DigitalMe (revision 2525 of IdentitySelector.js).
Although there are some additional features like the status-bar icon and the XRDS support.
Posted by
Unknown
at
5:05 AM
0
comments
Labels: bandit project, DigitalMe, openinfocard




