Office 2007 Product Key Windows Live ID - Windows

[kegen87247]

Many people today have asked a short time ago about the status on the Windows Live® ID local community technology preview (CTP) OpenID endpoints,Office 2007 Ultimate Keygen, so right here is often a swift update.

We gathered a great deal of outstanding feedback throughout the OpenID CTP period, and we've got fed that into our team's OpenID merchandise ideas. Thank you to every body who furnished input—you have directly impacted the solution!

The Manufacturing release of Windows Reside ID's OpenID Supplier assistance will glance substantially different through the CTP version, so we're within the practice of closing the OpenID CTP endpoints in order to avoid any confusion.

Currently, we don't have a schedule that I can publicly share for when we are going to release full Manufacturing assist of OpenID for Windows Reside ID consumers, but rest assured that we are doing work actively to provide OpenID features to all of our 500+ million Windows Dwell ID users,Office Professional!
Background: Our Approach inside CTP
A major characteristic of our OpenID Provider (OP) CTP was the attempt to use an account alias as both a “vanity URL” as well as a defense mechanism to help protect against phishing attacks.

In the CTP, Windows Dwell ID customers were required to create an OpenID alias (such as “http://openid.live.com/john”) attached to their account, and then to use that alias not just at the OpenID relying party site, but also as the way to identify themselves to the Windows Live ID OP. When arriving at the OP sign-in screen, users were required to enter their OpenID alias (instead of their normal Windows Reside ID user name) plus the password (or one of their other associated credentials, such as an Information Card) from their main Windows Stay ID account.
Why this approach?
One with the main things we were (and still are) trying to do with the Windows Dwell ID OP is to supply as much protection as possible to our Windows Reside ID end users against phishing attackers who use OpenID. OpenID does not support a network sign-out function as part of its protocol, which can mean that end users are left in a state that differs from what they might assume. For example, Windows Live ID consumers who sign out of an OpenID site might expect to be completely signed out of their account, because that is what happens on all other Windows Dwell ID-enabled sites.
How did it go?
We had envisaged that using an alias for OpenID sign-in could produce some separation for the two identity networks.
However, the usability model for this approach has turned out to be unfeasible and/or just plain confusing to customers,Windows 7 Home Basic!
Lessons Learned
So the main challenge uncovered while in the CTP was around aliasing, and then there was a grab bag of other things that we learned too.
Aliasing: a separate OpenID namespace for end users End users were confused about the need to associate a separate OpenID alias with their main Windows Dwell ID account. Users didn’t know where to go to create their OpenID alias; more setup pages to click through led to more drop-off. End users from diverse Windows Reside ID namespaces would be upset if they could not get the same alias as they already had. For example, john@hotmail.com and john@live.com and john@hotmail.co.uk could not all have the alias “http://openid.reside.com/john”. Acquiring all the “best” aliases quickly becomes overly competitive. Customers got confused about whether they needed to enter their OpenID alias or the user name of their main Windows Live ID account to sign in. Numerous end users forgot what their OpenID alias was, so we would have required a separate “alias recovery” technique. At the OpenID alias sign-in page, we would have had to present to consumers (and of course specifically test) all combinations of the various sign-in credential options that we already deliver for Windows Dwell ID accounts—going beyond user name and password to include smart cards, Information Cards, and other types of credentials. This complexity was pretty much a direct multiplier factor on the size from the required test matrix. Multiple entry-point paths Having multiple entry-point paths [for example, standard sign-in page + OpenID sign-in page + 3rd-party WebAuth sign-in + 3rd-party consent sign-in page] complicates all the sign-in interrupt flows that we must support. Preserving the user experience and familiarity across multiple entry-point paths is challenging if any or all could potentially be updated independently. The cost of always keeping multiple entry-point paths exactly in sync would have been too high. Any form of combined sign-in/authentication + consent/authorization flow would be also complicated if we now have multiple entry-point paths to deal with. Explaining things Last, but not least, we had a really hard time creating the right text to explain the choice between global unique alias and anonymous ID values being returned to relying party sites,Windows 7 Professional X86, even to super-geeks who work on identity software every day! Conclusion
Basically, then, end users will be able to use their existing Windows Reside ID account credentials to sign in to OpenID sites straight -- just like they at the moment can do for any sites already using Windows Dwell ID Web Authentication. End users won’t be required to pre-create a separate OpenID alias attached to their account in order to use it at OpenID sites.

We plan to optimize our manufacturing implementation around OpenID provider discovery / identity select features (enter stay.com within the OpenID sign-in box on a third-party site) as the best way forward for the vast majority of your consumers of our OpenID Supplier.

We will also aim to reuse and/or consolidate the various sign-in entry-point paths wherever possible -- to simplify the engineering and user experience for almost everyone.

Finally, we're planning to hide the choice of ID value / type to return to relying parties -- to simplify the overall user experience for our mainstream end users.

If you have any additional feedback on our lessons learned then you can send them to our OpenID Tech Preview Feedback address.
References OpenID Foundation Home Page http://OpenID.net Windows Reside ID Home Page http://dev.reside.com/liveid Original announcement for the Windows Live ID OpenID Supplier CTP http://winliveid.spaces.stay.com/blog/cns!AEE1BB0D86E23AAC,Office 2007 Product Key!1745.entry Windows Live ID Web Authentication SDK http://msdn.microsoft.com/en-us/library/bb676633.aspx