Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8216379
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 7, 20262026-06-07T12:06:21+00:00 2026-06-07T12:06:21+00:00

I am using DotNetOpenAuth to identify Google users. I am currently retrieving their e-mail

  • 0

I am using DotNetOpenAuth to identify Google users. I am currently retrieving their e-mail address and saving a copy of that in my database. However, what if they change their e-mail address in their Google account? Then my copy can no longer be linked to their profile.

Is there a way to uniquely identify a Google account through DotNetOpenAuth?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-07T12:06:22+00:00Added an answer on June 7, 2026 at 12:06 pm

    Always use the IAuthenticationResponse.ClaimedIdentifier to uniquely identify users!

    OpenID’s security model is based on this design. Using email addresses is insecure in many ways. Any Provider can issue a positive assertion claiming that the user owns a particular email address. OpenID doesn’t prevent the OP from lying about email addresses, so if you just used email addresses and the user key then you’d be wide open to user spoofing attacks. Even if the OP isn’t trying to be dishonest, you couldn’t generally trust it because you don’t know whether the OP verified the email address or simply asked the user what their email address was.

    Even if you trust Google to not lie, there are several reasons (some of them can be mitigated, but aren’t obvious) to not treat email address as the user identifier. For example, Google lets users change the email address behind their Google account. If the user did this and then returned to your web site, your site would identify them as a different user. Even worse, if another user later claimed a recycled email address for their new Google account, your site would recognize them as the older user and give the new user access to a bunch of old user data.

    OpenID Claimed Identifiers are designed to avoid all this trouble.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I'm using DotNetOpenAuth lib to work with Google(only) OpenId. And I'm retrieving Email without
I am running an issue with google openid identifier. I am using dotnetopenauth library
I'm using the sample provider and relying party applications that come in the DotNetOpenAuth
I'm using dotNetOpenAuth to authorise against Google oAuth provider. I'm a bit confused with
I am still reading on using dotnetopenauth and google openid. In the google docs
I'm trying to implement sign in with Google using Oauth (using DotNetOpenAuth). I need
I'm using DotNetOpenAuth with a custom login provider to sign users into my site.
I have been using DotNetOpenAuth v3.5.0.10357 for about a year now and finally decided
I am using DotNetOpenAuth in my ASP.Net Website. I have modified it to work
Introduction We have an OpenID Provider which we created using the DotNetOpenAuth component. Everything

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.