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 3752896
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 19, 20262026-05-19T09:18:30+00:00 2026-05-19T09:18:30+00:00

I am using dotnetopenauth and I am wondering what should I be storing from

  • 0

I am using dotnetopenauth and I am wondering what should I be storing from claimedIdentifier. I thought it would be just an id but it seems to have a url too.

When I do something like

Identifier claimedIdentifier = openIdRelayingParty.ClaimedIdentifier;

I get

//yahoo

https://me.yahoo.com/a/2RCv_bQ7341PA3v4irf5tzu_9K_fF1414afa414

// google

https://www.google.com/accounts/o8/id?id=AItOawmMvmoomT7lOO5jwEaAd1414dfafaf241VUI

So do I store this whole thing or just the long string? If I should store the the long string then how to I extract it out? It seems like each provider formatting is a bit different.

  • 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-05-19T09:18:31+00:00Added an answer on May 19, 2026 at 9:18 am

    You should store the entire URL, including the fragment part. The fragment part is the #fragment at the end of some URLs. For example, I think every Yahoo ClaimedIdentifier actually includes a fragment like this:

    https://me.yahoo.com/a/2RCv_bQ7341PA3v4irf5tzu_9K_fF1414afa414#aHd88

    It is vitally important that the entire ClaimedIdentifier be stored, and later used to identify the same person. Also, be sure your identity check is case sensitive. Do not use the System.Uri.Equals method to verify that two ClaimedIds are equivalent. It would return true in cases where only the #fragment is different, which is not correct. You should use Identifier.Equals or the simple String.Equals(string, string, StringComparison.Ordinal) method.

    Or if you’re looking up the user from your users table in a database, be certain that your users table is configured to be case sensitive for the ClaimedId column.

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

Sidebar

Related Questions

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
I'm using DotNetOpenAuth as my membership system, and the way I have it working
I have been using DotNetOpenAuth's OpenIdTextBox control on our login page. We used VS
I'm implementing an oauth provider using DotNetOpenAuth CTP library. So I have created an
I am using DotNetOpenAuth to authenticate an app on Windows Azure. From time to
Using dotnetopenauth, my code worked fine when using openId.CreateRequest(openIdIdentifier) . The return url was
I am using dotnetopenauth as an openid provider and have changed the Response.ApplyAppPathModifier file
I've just started using dotnetopenauth for my user registration. It's great, and is working

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.