Events for website owners who want to get out of the password business 5

The recent Sony incident was another wake up call for website owners about the problems with passwords as discussed in the recent OIDF blog post. One of the purposes of the OpenID Foundation blog is to help identify events that website owners can attend to learn more about alternatives to passwords.

There was one such event, called the Cloud Identity Summit, earlier this year that was so popular that a smaller version of the event is being run in four cities in the next few weeks.
• 10/24/11 New York, NY
• 10/25/11 Washington, DC
• 11/2/11 Chicago, IL
• 11/3/11 San Francisco, CA

You can learn more or register to attend at

The event will cover a number of topics that the OpenID Foundation is involved with including:
• Emerging standards such as OpenID Connect and its relation to OAuth
• User friendly ways to eliminate passwords using the Account Chooser technique
• Adoption of cloud identity standards in enterprise and citizen-government scenarios

If you’re a security architect, IT manager, SaaS product manager, eBusiness leader, CSO, CTO, or CIO leveraging the Cloud to change your business, it’s a day of identity security best practices you don’t want to miss.

Leave a comment

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

5 thoughts on “Events for website owners who want to get out of the password business

  • Kalie woods

    Who do I find out if someone as already used my name and emails for this open ID thing!!! Having trouble with a Hacker and not very good with computers!!! HELP PLEASSE

  • Shaun

    Do you think this breach of security will deter people from wanting a one pass? For example: one card thats your drivers license, your social security card, your bank card, your credit card, and your passport all rolled into one. Personally I think it’s a bad idea but I’m curious your thoughts on the matter.
    Thanks In Advance.

  • Nat Sakimura

    Personally, I think it is a bad idea to collapse all those credentials in one.
    I am not going to deep dive on it now, but IMHO, services with different risk level should have different credentials.
    Using “highly secure” credential for everything has unwanted cognitive load that leads the users to approve something they should not.