You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A community I represent has an incentive in it's community that allows contributors to our Folding Team (225605) to get a special tag that identifies them as part of the Folding team. The way we verify the user is part of the team was to ask the user to OAuth their Reddit account and provide their F@H Passkey to a connection site that we have built. This would link the two accounts and give the tag.
There does not appear to be a function of the new API (https://api.foldingathome.org/) to be able to query user data based on their passkey. This function is desired on our end because passkeys are private and only the user would know it instead of username which is public and anyone can claim. There's a level of validation to the passkey that isn't there with username.
A community I represent has an incentive in it's community that allows contributors to our Folding Team (225605) to get a special tag that identifies them as part of the Folding team. The way we verify the user is part of the team was to ask the user to OAuth their Reddit account and provide their F@H Passkey to a connection site that we have built. This would link the two accounts and give the tag.
There does not appear to be a function of the new API (https://api.foldingathome.org/) to be able to query user data based on their passkey. This function is desired on our end because passkeys are private and only the user would know it instead of username which is public and anyone can claim. There's a level of validation to the passkey that isn't there with username.
We used https://folding.stanford.edu/stats/api/donors?passkey= prior to that endpoint going away.
The text was updated successfully, but these errors were encountered: