http://blog.gmane.org/gmane.comp.web.openid.general hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.comp.web.openid.general/13852 <pre> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi there, I work for a company which is looking for a federation solution to SaaS applications used internally by the employees. For our use case is mandatory that the user data could keep in private and the SaaS provider must not have access to it. I was thinking to use OpenID because is well written and the most important part, it is an open-standard. For what I understood by reading the protocol specification, this is not a goal of OpenID. I would like to know if is possible to implement that kind of solution and If I'm not hurting the main project goals as long as I will not allow everyone to sign-in using an OpenID compatible account. Thanks. - -- Matheus Morais Infraestrutura de TI Confederação SICREDI ? Porto Alegre 51 3358-4700 ramal 7190 www.sicredi.com.br -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPqStQAAoJEJaxmh5NVUojoIcH/j7TLBPjfPZ1FXneJVU6UZ/Q bq06dx/uMlLt6702jvV+QhnkZvRdJDHPxkNjGYoUZCEu9lxLkddCMp/o6WiFvR7A oQZ8TDxlHmPzXf3Su3fb8kPnIvY6YmzP3ldjGl3XKXDXUs4bFnrrCNP3zE40Seut rzHtUoltWB7Q/Hv9a5Q8/dHhkSbPZVQVdDsd6JJpc8o0zMOEtoi2ncjIcbhNZyah 8Vy0gbeW6+futbAIJTFcfQtxr8hxRwcK7EqcyOv6f01IsD50UI+8KKbqEUMgBp90 xhf4yOYGCc/F6cnJWCJBF4QuZpIblRGUiCJ+7o29nGkTax09+Qo3CdMewZ4tbRo= =attP -----END PGP SIGNATURE----- Esta mensagem é somente para uso do destinatário informado e pode conter informações privilegiadas, proprietárias, ou privadas. Se você recebeu esta mensagem por engano, por favor notifique o remetente imediatamente e apague a original. Qualquer uso deste email é proibido. This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. </pre> Matheus Eduardo Bonifacio Morais 2012-05-08T14:18:57 http://comments.gmane.org/gmane.comp.web.openid.general/13850 <pre>Hi In my recnt work, I' ve done implementing OpenId OP/RP into NetCommons and Mediawiki. NetCommons is a Open Source LMS/CMS developed by NII(National Institute of Informatics of Japan). And Mediawiki is .... what you know, wiki system. As a result of that work, I'll have a presentation at the seminer named "NetCommons add-on module seminer" at 16th, Jun. In the presentation, I'll be talking about What is OpenID, How to implement it, and New topics about OpenID. Does anyone has suggestions What is hot or What is new about OpenID? please let me know. </pre> Toshiya TSURU 2012-05-08T04:21:10 http://comments.gmane.org/gmane.comp.web.openid.general/13845 <pre>Hi I'm concerned with my privacy and security, so I like the idea of OpenID accounts and I have a question: If I have OpenID account, how I can login in gmail with it? Because I want to use other OpenID, not the Google one... </pre> Mitaka 2012-04-10T11:40:02 http://comments.gmane.org/gmane.comp.web.openid.general/13844 <pre>What happens if I notice someone enabling OpenID (with delegation) in their page's headers, but get to account creation before they do? I'm admittedly confused by the myopenid.com signup process (just looking at its first page, here), but if someone else beats me to registration, will myopenid.com let me create a *second* account which works just as well as the first? Perhaps prove my control of the domain through OP-supplied nonces that show up in my OpenID headers later, to keep Eve from simply creating another account? Is the myopenid.com Username configurable (it doesn't say), or am I forever stuck with what Eve put there? (I'm beginning to think that it would be simpler if we just never let me alter my page headers until I had signed up with a provider. But then we have to create the infrastructure to let OP's control what HTML code I can put on my own webpages, so that doesn't seem practical either. The current arrangement seems to be "say nothing, lest actively discouraging it give users the wrong idea".) I'm looking at ClaimID's login/signup page, too. This is where I first began thinking of including the headers before a site was ready: for a movement that professes to care about "no registration", it sure seems kind of odd (to me) that the first thing we ask for (from users) is registration. (Sigh.) This is a bit of an impediment to my flow, from the tech end; if I'm going to sign up for an OpenID provider, why can't I do so with *my* OpenID? (Because, um, I don't *have* one yet? I do, but let's pretend that I don't.) I had somehow imagined it to be more streamlined: I add headers, and the provider confirms this. They see me coming (with redirect headers), they give me a deferral landing page that explains *why* they can't simply authenticate me straightaway, and *this* is where they tell me why they need various bits of information, and what they won't be able to do if I can't provide them with it. Of course, the real-internet *need* for this signup flow is negligible, I think - how many users *start* with adding headers to their page, instead of learning about OpenID through one of the many other channels? Also, there's the security risk of committing to your provider before you've established credentials with them, which may tip off an alert adversary (or anyone crawling your blog often enough to notice the *moment* you update it) that it's time to go sign up for an account before you do. Automation might make this a more feasible attack, but I still don't see it as a serious concern. I'm more bothered by the idea that someone might DoS a particular user by continually registering for the most popular providers, in their name, and thus always "obstructing the doorway" with their own (unguessable) password. -Shade </pre> SitG Admin 2012-04-09T11:20:10 http://comments.gmane.org/gmane.comp.web.openid.general/13837 <pre> ok Ill admit that we never "deployed" openid (as an IDP). I do have a nice codeplex project that is built on the 4windows openid library, that nicely emulates myopenid. But, Ive never had "need" to use it. We will see why below. As an SP, we can accept openid messages from Google, Yahoo, myopenid and openlink4webid (courtesy of the Microsoft Azure openid-&gt;ws-fedp bridge). Today, a nice demo has folks with Google crdentials using them to land on Joomla (that we properly ws-fedp enabled). Joomla plugins (wordpress and all its plugins, and JomSocial) then round out the user-centric experience. Since we bought into microsoft STS (passive) concept, the path from Google to Joomla actually wanders by other STSs, transparently. these create web-sessions in passing (and control flows, or add/transform claims). For exmaple, our realty authz claims inserted by an intermediated STS are mapped onto Joomla groups - which drives the flow in what is a now a 100% claims-drive website. Since folks have a google (and other sessions), mere hyperlinks from the SP site back to "pages" on the IDP sites (googe social, realty MLS, assocition-CRM) get folks a mashed-up webapp experience - without us acting an an openid token issuer. You already have those sessions! But, none of this gets me to the windows 8 tablet. The above is the web that was. What one thing can I do, for modern openid, in a windows 8 tablet world - that showcases openid (connect)? I probably have about 1 shot at inserting openid (connect) into a first release of a realty website tuned specifically to tablet-interaction dynamics. What can I do? There must be zero politics (dont sell me governance). There must be no strange .net languages (install Boo runtime on the tablet). There must be no third-party managed nascar array (full of politics and "control" of RP by IDPs issues). And, ideally, it would somehow showcase why openid is relevant to the device-centric "paradigm shift" - why openind is so totally relevant to a tablet-based UI concept (that looks like and behaves nothing like its PC desktop rendition). </pre> Peter Williams 2012-03-31T18:41:13 http://comments.gmane.org/gmane.comp.web.openid.general/13830 <pre>-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sorry for the crossposting. I am quite desperate :(. I haven't found a MyOpenID help email to address this. I have been using OpenID for ages, delegating from my own domain, http://www.jcea.es/, to MyOpenID. This delegation stopped working like two weeks ago, with the following error message (when redirected to MyOpenID to verify my OpenID, for example trying to login to StackOverflow): (the page title is "Bad Request") """ If you use OpenID delegation, please make sure your delegation information is set to &lt;a href="https://www.myopenid.com/help#own_domain"&gt;these values&lt;/a&gt;. """ The &lt;link&gt; headers in http://www.jcea.es/ seem OK: """ &lt;link rel="openid.server" href="http://www.myopenid.com/server" /&gt; &lt;!-- For delegating OpenID v1.x--&gt; &lt;link rel="openid.delegate" href="http://jcea.myopenid.com/" /&gt; &lt;!-- For delegating OpenID v1.x--&gt; &lt;link rel="openid2.local_id" href="http://jcea.myopenid.com" /&gt; &lt;link rel="openid2.provider" href="http://www.myopenid.com/server" /&gt; &lt;meta http-equiv="X-XRDS-Location" content="http://www.myopenid.com/xrds?username=jcea.myopenid.com" /&gt; &lt;!-- For delegating OpenID v2.x--&gt; """ This seems correct and consistent with MyOpenID instructions. This setup have been working for years. What is going on? Can you help me?. I would rather avoid to deploy my own OpenID server. If this is a MyOpenID problem, could you possibly suggest any other OpenID provider not linked to a facebook/twitter/wordpress/google/etc username?. Thanks in advance. - -- Jesus Cea Avion _/_/ _/_/_/ _/_/_/ jcea&lt; at &gt;jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ jabber / xmpp:jcea&lt; at &gt;jabber.org _/_/ _/_/ _/_/_/_/_/ . _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQCVAwUBT3O59plgi5GaxT1NAQLQlAP+KJoF7eialfESvvS4MMmvwbujQHpUErUb zZvDrrXnx382bE4UghK3v+Tg8RaPIbDFxWM8p3sdx5ZF771JRyZ82Bkw/RZANCh9 Zc7DIOYKCqdfUPAdxssGi4a9kuCT1uZWurY+jFX3+5RlEk8mYr1Y4YvYs3X044Jx 7nfLWdiVXcE= =3jwI -----END PGP SIGNATURE----- </pre> Jesus Cea 2012-03-29T01:25:10 http://comments.gmane.org/gmane.comp.web.openid.general/13829 <pre>Hi folks! I have been working on the IETF draft for OpenID in SASL: https://tools.ietf.org/html/draft-ietf-kitten-sasl-openid-08 and now also implemented it in GNU SASL, see this writeup: https://lists.gnu.org/archive/html/help-gsasl/2012-03/msg00004.html I wanted to reach out to the OpenID community to find people who want to work on implementing/deploying this. If you have some interest in implementing OpenID support for your SASL-based application (SMTP, IMAP, XMPP, etc) let me know and I will try to help. If anyone else has implemented the OPENID20 mechanism, I would also love to do interop testing. Cheers, /Simon </pre> Simon Josefsson 2012-03-28T19:29:19 http://comments.gmane.org/gmane.comp.web.openid.general/13828 <pre>The OIDF Account Chooser working group&lt;https://sites.google.com/site/oidfacwg/&gt;that got started in September 2011 &lt;https://sites.google.com/site/oidfacwg/wg-charter-note&gt; is now very close to launching the first version of a central Account Chooser service. This 4 minute video shows &lt;http://www.youtube.com/watch?v=lln11MRfpPw&gt; it working today and there are many demos you can try yourself&lt;https://sites.google.com/site/oidfacwg/cdsdemo&gt;. On March 22nd we are holding a meeting of the working group in Silicon Valley &lt;http://acwg2012march.eventbrite.com/&gt;, and others are invited to participate, including by watching a live video of the event&lt;http://acwg2012march.eventbrite.com/&gt; . This project has evolved in an unusual manner for the OIDF because it is primarily a service, not just a specification and open source code. So we are very interested in feedback from the community either at that event, on the ODIF general list, or on the working group list&lt;http://groups.google.com/group/oidf-account-chooser-list&gt;. The service is also protocol agnostic, meaning it works with OpenID, OpenIDConnect, SAML, and just about any login protocol. It even works for websites that still authenticate users with passwords. Google has been experimenting with an account chooser&lt;https://sites.google.com/site/gitooldocs/experiment---account-chooser&gt;since July 2011, and has found it works so well for our password based users that we are in the process of rolling it out first to that group, and only later going back to optimize it for people who log into Google via SAML, OpenID, etc. Eric Sachs Vice Chairman, OpenID Foundation Member of the OIDF Marketing Committee Member of the OIDF Account Chooser working group Senior Product Manager, Google _______________________________________________ general mailing list general&lt; at &gt;lists.openid.net http://lists.openid.net/mailman/listinfo/openid-general </pre> Eric Sachs 2012-03-08T20:49:30 http://comments.gmane.org/gmane.comp.web.openid.general/13827 <pre>Please help us get out the word that the OIDF is now starting to use social media to better communicate what we are doing, especially to websites owners who are still in the password business. There is also an effort underway to significantly update the OIDF website which will include better promotion of those social media channels. Until then, here are the links you can use. The Youtube channel in particular has been filled up with a lot of videos, and the G+ page links to other videos hosted elsewhere as well as information about the many upcoming OpenID events. - OpenID channel on Youtube&lt;http://www.youtube.com/user/TheOpenIDFoundation&gt; - OpenID page on Google+ &lt;https://plus.google.com/114852685785546775114&gt; - OpenID on Twitter &lt;https://twitter.com/openid&gt; - OpenID page on Facebook&lt;http://www.facebook.com/pages/OpenID/15157608236&gt; - OpenID group on Facebook &lt;http://www.facebook.com/groups/2250963308&gt; - OpenID group on Linkedin&lt;http://www.linkedin.com/groups?home=&amp;gid=40144&amp;trk=anet_ug_hm&gt; Eric Sachs Vice Chairman, OpenID Foundation Member of the OIDF Marketing Committee Member of the OIDF Account Chooser working group Senior Product Manager, Google _______________________________________________ general mailing list general&lt; at &gt;lists.openid.net http://lists.openid.net/mailman/listinfo/openid-general </pre> Eric Sachs 2012-03-08T20:48:27 http://comments.gmane.org/gmane.comp.web.openid.general/13826 <pre> This is to acknowledge the election of officers and Executive Committee of the 2012 Board of Directors of the OpenID Foundation. Last week, Nat Sakimura was reelected as Chairman of the Board. Nat continues to provide an invaluable continuity of leadership and representation for the OpenID Foundation in a wide variety of international standards organizations. Eric Sachs, Google's representative on the Board, was elected Vice Chairman. In addition to his Executive Committee responsibilities, Eric will continue to lead both the OIDF Marketing Committee and Account Chooser Work Group. Kick Willemse, was elected as Community Liaison. Kick will be providing the Foundation increased global awareness and much needed voice in the European marketplace. Kick and Eric's work with Nat will help guide important technical and adoption processes for the proposals and protocols in the OIDF pipeline; OpenID Connect - in the Implementer's draft stage, Account Chooser - ramping up for community input in 2012 and the nascent proposal around the "Backplane Exchange" Greg Keegstra is advocating. All these efforts point toward vibrant technical and marketing initiatives for the Foundation in 2012. John Bradley and Mike Jones were reelected as Treasurer and Secretary respectively. They make things happen. Mike and John have for many years gone to great lengths to be stewards of the OpenID protocol and the Foundation required to make it open to all. On behalf of the companies and community around open and user centric internet identity, we thank Nat, Eric, Kick, John and Mike in advance for their leadership. Don Thibeau The OpenID Foundation _______________________________________________ general mailing list general&lt; at &gt;lists.openid.net http://lists.openid.net/mailman/listinfo/openid-general </pre> Don Thibeau 2012-03-06T16:25:05 http://comments.gmane.org/gmane.comp.web.openid.general/13825 <pre>Does anyone know the owner of this Facebook page for OpenID: http://www.facebook.com/pages/OpenID/15157608236 The OIDF Marketing Committee is tracking down logins for the different social pages so we can start using them for marketing. We noticed that Facebook page already existed so we hoped to reuse it. Eric Sachs Vice Chairman, OpenID Foundation Senior Product Manager, Google _______________________________________________ general mailing list general&lt; at &gt;lists.openid.net http://lists.openid.net/mailman/listinfo/openid-general </pre> Eric Sachs 2012-03-02T17:25:24 http://comments.gmane.org/gmane.comp.web.openid.general/13817 <pre> I briefly reviewed the openid connect specs (not having seen drafts for years), a rather strange lightweight PKI spec (RFC 6125) that seemed to make rather a mess out of settled engineering material of key management, a reference to an ITU-T spec (whose text I could not read), and OAUTH v2 specs. I looked at it all as one family - defining a new generic upper layer protocol spec. It was clearly pointless trying to comprehend the anticipated reach or inner nature of openid connect without embracing the wider context. Having worked with auditors and lawyers 15 years ago to write practice disclosures and then actual contracts for the then highly-engineered and internet-centric (vs web-centric) world of TLS, OCSP, and CMS and authenticode timestamping, I asked myself: could you reduce openid connect and all its supporting architectural and dependent infrastructure references to what THEY need? (knowing well how they think, at this point). Could I get to the core model? Could I translate it into the (declarative) language of legal or audit-testing protocols? I decided the answer was yes, but it would take several months of work - mostly sorting through the morass and reducing it to declarative claims and or statements. I could only do it for a profile of the morass, though, and could not do it for the general case. (This is an innocuous but actually key observation, that comes only with considerable experience). Some of the material is almost still "work in progress", and there is a lot of duplication and overlap with older generation of specifications. There is also a not inconsiderable amount of architectural posturing at times, as I found folks reaching for a tone that defines "what's different?" and justifies "why improve what's settled?" - since there really does seem to be 1 step forward 2 steps back, at times. As I was doing this, I kept saying to myself... well I see folks really are attempting to build a new layer 5-7 upper layer protocol spec...and I see that it is in many ways merely a lightweight profile of stuff that already exists (much like ldap dumbed-down X.500 in the 90s, or SMTP dumbed-down MTP in the 80s), but I pity the non-specialist who is tasked with trawling through it. Its really not that lightweight, it just a different tone. And its a tone that justifies itself because the character of the problem really has changed. If I had to answer the question to a non tecehnical person: why does it all exist (and what motivates it the change of tone)? I think the only 10 word answer I could give is: well the iphone changed the web. No longer is there only the hypermedia web browser. Now there is the iphone client too, and the web will never go back to being what it was (as originally conceived with the single, universal access device, hopping around from here to there, with limitless abandon, while you sit at a desk). And, so the internet/web security layer has had to evolve too ...to work with this new category of telematic client. And thus the security model (that was all tuned up for the presumptions of the document-centric, hypermedia-viewing web browser, and the web architecture) has had to change too. The e book client (in the nook product, say) is another example of a non-web browser that acts as an access device for the web, featuring a managed interaction model. If you have the knowhow and experience to map features from the older heavyweight techniques and method to their lightweight versions, it does get easier to comprehend. And, this does allow one then to map what appears new (but really is not) onto the established legal and auditor protocols (and consequently write something that would pass the legal review or audit disclosure examinations). it is possible to strip it all down and free it of the technicalities and the new pseudo-design vocabulary, and reduce it all to controls and claims. I found the openid connect documents readable. But they do require a fair amount of context to be comprehensible. I found myself tending at times to say: ah that's just [this old thing] recast [as this new thing] - which did help comprehension (when wanting to map them down to their legal protocol equivalents, and borrow from older practices documents). I could kinda see where some political alliances have forced certain material together (often in ungainly fashion). But, when read it all as a set, I could see and grasp at the "generational shift" that is driving the change. Its hard to see it character at times (and folks seem to groping for a consistent language for its distinctive tone), but it is there. I could feel the pulse of the social movement (and didn't find myself rejecting it) . Its quite fun to then look back and say: well was that what I expected for openid? then answer is no, I didn't have any idea when I wandered into an openid session at a DigitalId world that this is what folks were contemplating. And, this observation is a little disconcerting (but not wholly unacceptable). I am glad we never deployed authenticated comments, OAUTH API endpoints, or used URI-based login dialogues (or NASCARs)m or bought into the minimalist UI theming trends. But I do find myself wanting to get out my compiler and apply some of the stuff FOR its architectural features. The specs worked therefore, in the evangelism sense, even though I found at my stage of programming capabilities engineering pining for the nice simple microsoft "scaffolding" code that will reduce all the com plexity (of OAUTH v1.x) for the likes of me to simple to understand models (using the firm's cloud-based STS "delivery vehicle") Finally, it helped looking at the technology through the lens of NSTIC - imagining these documents and those of the supporting specs evolving into a settled national identity framework, with the robustness of the old phone system. And, I can see it happening. I can see why the generational shift is required, having grasped at the limits that folks are articulating as justicication for why the renewal process is required. I do see that there is an generic upper layer identity layer that was just not there in the design forums of 20 years ago (though ITU-T-era engineers broke the ground we are now standing on, characterizing an earlier veresion of the problem). And, I sense that quite different grade of engineering is ultimately involved, and its focused on a level of "globally managed" inte rworking that simply didn't exist -- in the first few generations of the web. </pre> Peter Williams 2012-02-17T11:54:58 http://comments.gmane.org/gmane.comp.web.openid.general/13816 <pre>Dear OpenID Fans: The OpenID membership has approved the following specifications as OpenID Implementer’s Drafts in the vote held from February 7th to 15th, 2012&lt;https://openid.net/foundation/members/polls/62&gt; at https://openid.net/foundation/members/polls/62: • Basic Client Profile – Simple self-contained specification for a web-based Relying Party. (This spec contains a subset of the information in Messages and Standard.) • Discovery – Defines how user and provider endpoints can be dynamically discovered. • Dynamic Registration – Defines how clients can dynamically register with OpenID Providers. • Messages – Defines all the messages that are used in OpenID Connect. (These messages are used by the Standard binding.) • Standard – Complete HTTP binding of the Messages, for both Relying Parties and OpenID Providers. • Multiple Response Type Encoding – Registers OAuth 2.0 response_type values used by OpenID Connect. The voting results were: - Approve (86 votes) - Disapprove (1 vote) - Abstain (2 votes) Total Votes: 89 (out of 363 members = 25% &gt; 20% quorum requirement) An Implementer’s Draft is a stable version of a specification providing intellectual property protections to implementers of the specification. The specifications are posted at these locations: • http://openid.net/specs/openid-connect-basic-1_0-15.html • http://openid.net/specs/openid-connect-discovery-1_0-07.html • http://openid.net/specs/openid-connect-registration-1_0-08.html • http://openid.net/specs/openid-connect-messages-1_0-07.html • http://openid.net/specs/openid-connect-standard-1_0-07.html • http://openid.net/specs/oauth-v2-multiple-response-types-1_0-03.html A description of OpenID Connect can be found at http://openid.net/connect/. The working group page is http://openid.net/wg/connect/. Enjoy! Nat Sakimura (=nat) Chairman, OpenID Foundation http://nat.sakimura.org/ &lt; at &gt;_nat_en _______________________________________________ general mailing list general&lt; at &gt;lists.openid.net http://lists.openid.net/mailman/listinfo/openid-general </pre> Nat Sakimura 2012-02-17T06:25:57 http://comments.gmane.org/gmane.comp.web.openid.general/13784 <pre>The vote for the OpenID Connect for Implementer's Draft closes tomorrow. We are just a few vote shy of making the quorum. If you do not fully understand the draft, that's OK. Just vote abstain. Or you can vote "No". Making the quorum is what matters. You can vote from here: https://openid.net/foundation/members/polls/62 Don Thibeau The OpenID Foundation _______________________________________________ general mailing list general&lt; at &gt;lists.openid.net http://lists.openid.net/mailman/listinfo/openid-general </pre> Don Thibeau 2012-02-14T22:54:11 http://comments.gmane.org/gmane.comp.web.openid.general/13782 <pre>If you haven't voted already, please do so now at https://openid.net/foundation/members/polls/62. The voting period ends tomorrow. For more information, go to http://openid.net/2012/02/07/vote-for-openid-connect-implementers-drafts-are-open/. Thanks, -- Mike _______________________________________________ general mailing list general&lt; at &gt;lists.openid.net http://lists.openid.net/mailman/listinfo/openid-general </pre> Mike Jones 2012-02-14T21:30:44 http://comments.gmane.org/gmane.comp.web.openid.general/13761 <pre>FYI: One-Click OpenID: A Solution to the NASCAR Problem, blog post at http://pomcor.com/2012/02/13/one-click-openid-a-solution-to-the-nascar-problem/ Comments welcome. Francisco Francisco Corella, PhD Founder &amp; CTO, Pomcor Twitter: &lt; at &gt;fcorella Blog: http://pomcor.com/blog/ Web site: http://pomcor.com_______________________________________________ general mailing list general&lt; at &gt;lists.openid.net http://lists.openid.net/mailman/listinfo/openid-general </pre> Francisco Corella 2012-02-14T01:00:32 http://comments.gmane.org/gmane.comp.web.openid.general/13758 <pre> OpenID Foundation 2012 Community Board Member Election Results Thanks to all who voted for the board members who will represent the OpenID community at large for the next two years. Having received the two highest number of votes cast, Greg Keegstra and Axel Nennker have been elected to two years terms. Greg is new to the board and brings a fresh eye to OpenID marketing and outreach. Axel is a returning community board member, bringing his technical expertise in mobile identity research and an informed European perspective to the Foundation. They join current community representatives John Bradley, Mike Jones, Nat Sakimura, and Kick Willemse, serving the second years of their terms. Their leadership, together with sustaining member company representatives; Pam Dingle of Ping Identity, Farhang Kassaei of PayPal, Tony Nadalin of Microsoft, Nico Popp of Symantec, and Eric Sachs of Google was important to the success of last years OpenID Connect Summits. This is a good time to thank Brian Kissel, Chris Messina, and Allen Tom for their service to the Foundation and the OpenID community. Brian's leadership as Chairman of the Board was crucial to managing the Foundation's transition from its community roots to where we are today. Chris Messina's marketing sense and Allen Tom's technical chops went a long way towards maintaining OIDF's user centric perspective and industry influence. Last year, Dave Recordon and I often talked about how the OpenID Foundation should evolve. My view was that OpenID does indeed have a "second act" and that the Foundation's leadership of open identity standards development is important in a rapidly changing internet identity ecosystem. The sponsorship and attendance at the OpenID Summits, the hard work of the OpenID Connect WG and the promise of "Account Chooser" all indicate there is much to do and look forward to in 2012. It will be a pivotal year for OpenID and digital identity. The new board's first meeting on March 1 will consider long term operational and strategic issues. Feel free to make your thoughts known on this list, by contacting community representatives or me Don Thibeau Executive Director The OpenID Foundation Don Thibeau The OpenID Foundation _______________________________________________ general mailing list general&lt; at &gt;lists.openid.net http://lists.openid.net/mailman/listinfo/openid-general </pre> Don Thibeau 2012-02-13T11:59:24 http://comments.gmane.org/gmane.comp.web.openid.general/13745 <pre>FYI: http://pomcor.com/2012/02/10/openid-providers-invited-to-join-in-an-nstic-pilot-proposal/ _______________________________________________ general mailing list general&lt; at &gt;lists.openid.net http://lists.openid.net/mailman/listinfo/openid-general </pre> Francisco Corella 2012-02-10T23:58:03 http://comments.gmane.org/gmane.comp.web.openid.general/13741 <pre>This is a message regarding the upcoming OpenID Board of Directors election. Chris Messina has decided not to run for re-election in 2012. I want to acknowledge the important contributions Chris has made from the beginning of the OpenID effort. As a community board representative and member of the Executive Committee, Chris has shared his considerable network, marketing expertise and strong views about user-centric identity. As Chris has said; "internet identity continues to be an unsolved problem for the mass of free (as in freedom) internet users." Chris's contributions act as model for others to step up to the important contributions that can be made as a community director on the OpenID Foundation Board. To be sure, leadership and collaboration with competitors on industry standards has built in challenges, especially for those representing a broad community interest. In this context the voice of the community is especially important. A concrete and recent lesson lies in the evolution to OpenID Connect and how collaboration of community contribution and among unlikely allies like Facebook, Google, and Microsoft is changing online identity. 2012 will be a pivotal year. OpenID Connect global adoption will begin, Google's transfer of its Account Chooser IPR to the foundation will be determined and work on new protocols is expected. On behalf of the Board and the OpenID community, we thank Chris for his service. We ask OpenID Foundation members to encourage your colleagues to step forward for election and most important participate in the upcoming vote. Contact me if you have any questions. Don Thibeau Executive Director OpenID Foundation don&lt; at &gt;oidf.org _______________________________________________ general mailing list general&lt; at &gt;lists.openid.net http://lists.openid.net/mailman/listinfo/openid-general </pre> Don Thibeau 2012-01-05T20:11:09 http://comments.gmane.org/gmane.comp.web.openid.general/13741 <pre>This is a message regarding the upcoming OpenID Board of Directors election. Chris Messina has decided not to run for re-election in 2012. I want to acknowledge the important contributions Chris has made from the beginning of the OpenID effort. As a community board representative and member of the Executive Committee, Chris has shared his considerable network, marketing expertise and strong views about user-centric identity. As Chris has said; "internet identity continues to be an unsolved problem for the mass of free (as in freedom) internet users." Chris's contributions act as model for others to step up to the important contributions that can be made as a community director on the OpenID Foundation Board. To be sure, leadership and collaboration with competitors on industry standards has built in challenges, especially for those representing a broad community interest. In this context the voice of the community is especially important. A concrete and recent lesson lies in the evolution to OpenID Connect and how collaboration of community contribution and among unlikely allies like Facebook, Google, and Microsoft is changing online identity. 2012 will be a pivotal year. OpenID Connect global adoption will begin, Google's transfer of its Account Chooser IPR to the foundation will be determined and work on new protocols is expected. On behalf of the Board and the OpenID community, we thank Chris for his service. We ask OpenID Foundation members to encourage your colleagues to step forward for election and most important participate in the upcoming vote. Contact me if you have any questions. Don Thibeau Executive Director OpenID Foundation don&lt; at &gt;oidf.org _______________________________________________ general mailing list general&lt; at &gt;lists.openid.net http://lists.openid.net/mailman/listinfo/openid-general </pre> Don Thibeau 2012-01-05T20:11:09 http://comments.gmane.org/gmane.comp.web.openid.general/13741 <pre>This is a message regarding the upcoming OpenID Board of Directors election. Chris Messina has decided not to run for re-election in 2012. I want to acknowledge the important contributions Chris has made from the beginning of the OpenID effort. As a community board representative and member of the Executive Committee, Chris has shared his considerable network, marketing expertise and strong views about user-centric identity. As Chris has said; "internet identity continues to be an unsolved problem for the mass of free (as in freedom) internet users." Chris's contributions act as model for others to step up to the important contributions that can be made as a community director on the OpenID Foundation Board. To be sure, leadership and collaboration with competitors on industry standards has built in challenges, especially for those representing a broad community interest. In this context the voice of the community is especially important. A concrete and recent lesson lies in the evolution to OpenID Connect and how collaboration of community contribution and among unlikely allies like Facebook, Google, and Microsoft is changing online identity. 2012 will be a pivotal year. OpenID Connect global adoption will begin, Google's transfer of its Account Chooser IPR to the foundation will be determined and work on new protocols is expected. On behalf of the Board and the OpenID community, we thank Chris for his service. We ask OpenID Foundation members to encourage your colleagues to step forward for election and most important participate in the upcoming vote. Contact me if you have any questions. Don Thibeau Executive Director OpenID Foundation don&lt; at &gt;oidf.org _______________________________________________ general mailing list general&lt; at &gt;lists.openid.net http://lists.openid.net/mailman/listinfo/openid-general </pre> Don Thibeau 2012-01-05T20:11:09 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.web.openid.general