4
2

We are considering moving a StackExchange site to OSQA but in doing so we want the users of the StackExchange site to be able to continue to use the same OpenID account in OSQA. If not the same OpenID account then at least be able to retain the same Screen Name and/or internal user id. The intent is that we would like the users to be able to keep their reputation points, etc.

Has some thought been given to how this might be accomplished?


After some more research I think there is a way of doing it:

  • to start, users must have their email addresses known within the SE database
  • move the SE data to OSQA
  • the first time a user visits the new OSQA site the user must request to login and then click the "Help" link and then enter their email address that was within the original SE site
  • a temporary link will be sent to the person via email
  • the user receives the email and clicks on the link and as a result gets logged into the new OSQA site
  • the person then edits their user profile and deletes the original OpenID provider (that was used by SE) and adds a new provider (or just enters a password) thus allowing the OSQA site to be able to authenticate the user directly in the future

Is this sounds right?

asked 08 Jul '10, 17:14

Mark%20Culp's gravatar image

Mark Culp
61124
accept rate: 0%

edited 08 Jul '10, 18:14


There are lots of SX sites running OSQA now including some of the biggest ones, and generally everything ran smoothly. Only data that is not possible to import is user favorite questions and favorite tags, due to the fact that is not present in the data dump, other than that even custom html and static pages are imported.

link

answered 08 Jul '10, 18:10

Hernani%20Cerqueira's gravatar image

Hernani Cerq... ♦♦
16.8k65975
accept rate: 52%

Ok, so you are saying that the OpenID authentication should just work? I've tried it and had problems so maybe something else is going wrong - I will have to investigate further?

(08 Jul '10, 18:16) Mark Culp
(08 Jul '10, 18:17) ripper234 ♦

@ripper234, not sure if I can do that. Some of the site owners may not like it, with the exception of <http:/ask.sqlservercentral.com> which is visible in lots of questions and comments here. There is also http://nullpointer.ph, which I guess it's also visible in some of the posts here, but that is not one of the biggest sites, but they did a great job with it btw :)

Dunno how you would like to organize such a listing, so I'll leave it up to you.

(08 Jul '10, 18:37) Hernani Cerq... ♦♦
1

@Mark, you might experience problems with google or yahoo, but only if you also alter your domain. But if you keep it than there shouldn't be any problems. If you have any problem, those steps you described are generally correct.

(08 Jul '10, 18:38) Hernani Cerq... ♦♦

@Hernâni: We are changing domains so that is likely the issue. Thanks.

(09 Jul '10, 07:44) Mark Culp

@Mark Culp, the Google OpenID authenticator is the strictest we have encountered, and it even distinguishes between domain.com and www.domain.com - so we recommend that you pick one of the two and redirect the other to it using an apache mod_rewrite rule. Anyway, your users should mostly be able to have a smooth transition, and we will help you help any of them who don't.

(09 Jul '10, 10:58) rickross ♦♦
showing 5 of 6 show 1 more comments

We at NullPointer.ph actually encountered problems with regards to the OpenID of our users who were using Google and Yahoo OpenIDs. The problem existed even if we were already using our original domain which was http://nullpointer.ph/.

What we did to solve the problem was ask our users to send their myOpenID usernames, replace the OpenID provider that our users are using for their existing NullPointer.ph accounts using their myOpenID since the myOpenID url is the same as its key unlike Google and Yahoo that varies for each domain. After that, our users can login at NullPointer.ph using their myOpenID account. Then they can simply add Google or Yahoo as a new provider under the User Tools in your NullPointer.ph profile.

It's an ugly solution but it solved the problem. Every other relevant data was preserved and we're happy for that.

link

answered 08 Jul '10, 23:09

Randell's gravatar image

Randell
2.0k479376
accept rate: 28%

edited 08 Jul '10, 23:10

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×40
×38
×32
×18

Asked: 08 Jul '10, 17:14

Seen: 577 times

Last updated: 09 Jul '10, 10:58

powered by OSQA