Blog Archive February (12) January (12) December (16) November (19) October (13) September (19) August (19) July (14) June (13) May (45) April (18) March (15) February (11) January (6) December (8) November (12) October (7) September (18) August (9) July (8) June (23) May (43) April (11) March (14) February (10) January (6) December (13) November (10) October (11) September (10) August (10) July (13) June (22) May (36) April (31) March (16) February (9) January (5) December (11) November (7) October (9) September (8) August (9) July (11) June (10) May (10) April (16) March (16) February (7) January (10) December (8) November (13) October (16) September (11) August (16) July (11) June (14) May (13) April (12) March (19) February (14) January (12) December (10) November (14) October (13) September (11) August (14) July (9) June (5) May (5) April (6) March (4) February (2) January (5) December (4) November (1) October (3) September (2) August (5) July (3) June (11) May (2) April (4) March (5)
We're happy to announce that the Google OpenID Federated Login API has been extended to Google Apps accounts used by businesses, schools, and other organizations. Individuals in these organizations can now sign in to third party websites using their Google Apps account, without sharing their credentials with third parties.
In addition, Google Apps can now become an identity hub for multiple SaaS providers, simplifying identity management for organizations. For example, when integrated with partner solutions such as PingConnect from Ping Identity, the Google Open ID Federated Login API enables a single Google Apps login to help provide secure access to services like Salesforce.com, SuccessFactors, and WebEX — as well as B2B partners, internal applications, and of course consumer web sites. See Ping Identity's post to learn more about their implementation and view the demo.
Another early adopter is Manymoon.com, a SaaS project management vendor that implemented the Google Open ID Federated Login API directly to make it easier for any organization using Google Apps to sign up for and deploy Manymoon to their users:
The user types in his Google Apps email address. The user never gives away his Google Apps Account password to Manymoon.
Once approved, the user is redirected to Manymoon and is signed in and ready to work with selected accounts.
If you prefer an out-of-the-box solution, we have been working with JanRain, a provider of OpenID solutions that already supports the new API as part of their RPX product.
Supporting the API for Google Apps accounts is exciting news for the OpenID community, as it adds numerous new Identity Provider (IDP) domains and increases the OpenID end user base by millions. In order to allow websites to easily become Relying Parties for these many new IDPs and users, we defined a new discovery protocol. The protocol is designed to allow Relying Parties to identify that a given domain is hosted on Google Apps and to help provide secure access its OpenID Provider End Point. The current proposal is an interim solution, and we are participating in several standardization organizations, such as OASIS and the OpenID Foundation, to generate a next-generation standard. Since the current protocol proposal is not supported by the standard OpenID libraries, we provided an implementation of the Relying Party pieces at the Open Source project, step2.googlecode.com. Google is also offering a set of resources addressing the issues of designing a scalable Federated Login User Interface. You are welcome to visit the User Experience summary for Federated Login Google Sites page, where you can find links to demos, mocks, and usability research data.
You can find more details in our API and Discovery documentation, or join the discussions in the Google Federated Login API Group, where you can ask any question and get answers from other Identity Providers, Relying Parties and Google engineers.
The OpenID Federated Login Service is available for all Google Apps editions. However, it is disabled by default for the Premier and Education editions, and it requires the domain administrator to manually enable it from the Control Panel. We've enabled the service for our employees here at Google, and domain administrators — you can also enable it for your domain.
Next up, can we see Google (Apps) accounts become a relying party, i.e. accept OpenID credentials from other OpenID providers? That would obviously be opt-in also but would encourage more widespread OpenID adoption.
This feature is great for Google Apps. Is there a overview of all sites I granted access? In Google Accounts you have My Account > Change authorized websites.
Why? Because if I'm going to leverage my google account login to login to a bunch of other web sites, then it's important to me to apply an extra layer of security that you get with two-factor authentication.
There are software versions of OATH tokens for smart phones like the iPhone, so no hardware token would be required.
You can get OATH and various other types of strong authentication (via SAML IdP to Google Apps) from 3rd party service providers. The www.myonelogin.com solution offers many multi-factor authentication options. A full list of MFA solutions can be found at the Google Marketplace:
To view and manage the list of websites you granted access, simply go to: www.google.com/a/example.com/ManageAccount (replacing "example.com" with your domain) and click on the "Change authorized websites" link
Anything announced for individual Google accounts vs. a Google App account? Would love to see this feature extended/offered to individuals, allowing them to centrally manage their SaaS application credentials.
The Google Federated Login already existed for regular GMail accounts. This post just notes they not have it for Google Apps accounts as well now.
I posted a tutorial on how to use your domain name as your OpenID URI with Google Apps since I couldn't find it in Google's documentation: http://jeremiahlee.com/blog/2009/09/28/how-to-setup-openid-with-google-apps/
There are much better providers out there than Google, which is plain old usernames and passwords. Personally, I use VeriSign PIP, which has two factor authentication using a wallet sized card that PayPal sells for $5.
Unique ford Focus 2015 Review is free HD wallpaper. This wallpaper was upload at February 5, 2018 upload by admin96 in ford focus.
You can download Unique ford Focus 2015 Review in your computer by clicking resolution image in Download by size:. Don't forget to rate and comment if you interest with this wallpaper.
Thank you for visiting my blog and reading in this post ,i love sharing what i do and hope that contents of my blog are inspiring to you. Unless stated. All the work on my blog is of my own creation,i encourage you use the creations i share howover suits you best.the content is my sole responsibility as an independent stampin up. Creativity is all about sharing the art we enjoy and i am delight if i am part of that proces for you.If you share any of my work and would like to link back to my blog – thank you.
DISCLAIMER: All background wallpapers found here are believed to be in the "public domain". If you believe that any of background/wallpapers posted here belongs to your site and you do not want it to be displayed on our site or you want us to link back to your site, then please contact us and we will take action immediately. We will either remove the background/wallpaper or provide credit to your site. We believe in entertaining world and therefore we provide all the background/wallpapers free or charge and gain no financial benefit.