The links to create a partner access account with Findmypast is broken. When you attempt, you get an

LegacyUser

Gaylon Findlay said: Go to Help in FamilySearch, click on the "Partners" icon in the list of help center icons, click on "Partner Access", under "Findmypast", click on "Join for Free", click on either "Create ..." or "Sign In...", and you get an OAUTH2 error. You can create an account re sign in.

LegacyUser

A van Helsdingen said: Are you a member of the Church of Jesus Christ of Latter Day Saints? The partnership between FMP and FS only permits LDS members to have free accounts.

LegacyUser

Gaylon Findlay said: Yes.

I am also the developer of Ancestral Quest, and the primary developer of PAF 5.

Members of the Church, who use our software to provide Hints from Findmypast, are reporting that they can no longer get access to records from Findmypast, as there seems to be a problem.

I also went to the FamilySearch.org/tree page, and tried to do a search on Findmypast from the Search section of the person details page. I can no longer view records when the search is initiated from FamilySearch.org/tree.

LegacyUser

A van Helsdingen said: I'd guess either:
1. There is a technical/software issue (most likely)
2. The records in question are no longer available to LDS free accounts. When the partnership started, "99%" of records on FMP, Ancestry, MyHeritage etc were available via the free LDS accounts. The owners of many records have since opted-out, and demanded that only paying customers can view their records.
3. The partnership has quietly been suspended or terminated (seems unlikely given the lack of announcement)

LegacyUser

joe martel said: Coming from the partner access page I get the oath2 error as well.

I tried this the Search from the Persons Details page work for both member and public accounts.
Sometimes the authentication can get goofed up by browser cookies and such.

This has been forwarded on to the partner team.

LegacyUser

jimmy.zimmerman said: This was a technical configuration problem. The problem has been fixed now. Please try again.

LegacyUser

Gaylon Findlay said: Jimmy:

Thanks, that solved it.

Gaylon