An exclusive gaming industry community targeted
to, and designed for Professionals, Businesses
and Students in the sectors and industries
of Gaming, New Media and the Web, all closely
related with it's Business and Industry.
A Rich content driven service including articles,
contributed discussion, news, reviews, networking, downloads,
and debate.
We strive to cater for cultural influencers,
technology decision makers, early adopters and business leaders in the gaming industry.
A medium to share your or contribute your ideas,
experiences, questions and point of view or network
with other colleagues here at iVirtua Community.
You can now allow your users on websites and forums to sign in withtheir windows live ID, this move by Microsoft makes your website muchmore open to those 100 million Live users out there.
The system works in conjunction with your website allowing each Live IDuser to login each time with their email and current Live ID password.
Other features allow user to chat with their contacts through yourwebsite and send predefinied emails (by you) to their contacts.
Whats great about this new SDK is that there allowing development on ASP.NET, Java, Perl, PHP,Python, and Ruby
You can download it here and read the documentation here.
Mashable.com read our article, and picked up on the fact that Windows Live login could hurt OpenID.
Mashable.com wrote:
Similar to Yahoo, sign-in and account management is handled byWindows Live ID, leaving fewer details to be performed on your end. TheWindows Live ID application can be implemented in ASP.NET, Java, Perl,PHP, Python and Ruby. Additionally, you can enable your users to chatwith their Windows Live contacts, as well as send basic messages, viayour website, to their friends.
Another service that offers this tool is OpenID, which is stillgrowing its user base and has fewer integrated options. With companieslike Microsoft offering Web ID authentication options, developers aremore able to leverage an existing user base, as opposed to starting atthe ground level, growing alongside another start up. WikiSpaces and Plaxo are both companies that have recently added OpenID support.
You can now allow your users on websites and forums to sign in with their windows live ID, this move by Microsoft makes your website much more open to those 100 million Live users out there.
The system works in conjunction with your website allowing each Live IDuser to login each time with their email and current Live ID password.
Other features allow user to chat with their contacts through your website and send predefinied emails (by you) to their contacts.
Whats great about this new SDK is that there allowing development on ASP.NET, Java, Perl, PHP,Python, and Ruby
Quote:
The Windows Live ID Web Authentication SDK describes a platform-independent interface for implementing Windows Live ID sign-in on Web sites of all kinds. This release includes a sample application for each of six different programming languages: ASP.NET, Java, Perl, PHP, Python, and Ruby. For each language there is a function library that you can use to extend the sample.
With Windows Live ID Web Authentication, you can use the Windows Live ID service to verify the identity of visitors to your site, so that you can offer personalized access to your site’s content by the millions of registered Windows Live ID users. Windows Live ID provides you with a unique, site-specific identifier for each Windows Live user who signs in to your site. Web Authentication also enables you to incorporate Windows Live controls into your site.
It's easy to start using the Windows Live ID service on your site. The following steps outline the six general tasks involved in implementing Web Authentication:
1. Register your application. For details, see Getting Your Application ID for Web Authentication.
Note:
You do not need to register to run the QuickStart samples, but you must register before you can extend the samples for use on your live Web site.
2. Install and run the QuickStart sample application for your platform. For details, see QuickStart Samples for Web Authentication.
3. Display the Sign in link on your page. For details, see Displaying the Sign-in Link.
4. Decrypt the token returned by Windows Live ID to obtain the user's unique identifier. In the sample application, the token is stored in a session cookie called "webauthtoken" to keep the user signed in to your site across multiple page views. For details, see Handling the Response from the Service.
5. Display or store content or personalized data and settings—for example, Windows Live controls—for your user, based on your site's security policies. For details, see Incorporating Windows Live Controls.
6. Sign the user out. For details, see Handling the Response from the Service.