WordPress signin in a multi-instance environment
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- wordpress
- Domain
- authentication, databases
Research direction
Start by reading the confirmation changes described for feedland, daveappserver, and wpidentity, including versions 0.6.22, 0.7.12, and 0.4.11. Done means WordPress signin confirmations are stored in the shared database and work across instances when config.flUseDatabaseForConfirmations is true.
Written by the indexing model from the issue text.
Description
I announced on Sunday that I've been working with people at Automattic to make it possible to run FeedLand on a server that can scale to millions of users. That means that you can't rely on any info that stored in the local memory of one instance, because the response may come from a different instance. This issue has come up over and over, and it comes up in the case of WordPress login.
Previously I was sending a random number as the key value that confirms that the request to log in with WordPress came from FeedLand. To do that in the new context, the key value has to be stored in the database, so it's equally accessible to all instances.
I used the same confirmation system that we use for email identity, that meant changes to feedland, daveappserver and wpidentity versions 0.6.22, 0.7.12 and 0.4.11.
Note -- to get this functionality you must set config.flUseDatabaseForConfirmations to true.
- Dominant language
- HTML
- Stars
- 11
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from scripting/feedlandInstall
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
scripting/feedlandInstall#75 · 3 comments · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
scripting/feedlandInstall#79 · 1 comment · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
scripting/feedlandInstall#77 · 3 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
scripting/feedlandInstall#76 · 3 comments ·
-
Difficulty 1/5 Under an hour Newbie friendliness 20/100
scripting/feedlandInstall#74 · 3 comments ·
All issues in scripting/feedlandInstall
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
getgrav/grav-plugin-api#45 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sisaku-security/sisakulint#647 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
yunaremaia/driftcheck#246 ·
-
Docs say approvals.mode defaults to smart, but code falls back to manual when the key is absent Openarea/config comp/tools P2 sweeper:risk-compatibility type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
NousResearch/hermes-agent#117341 · 1 comment ·
-
bug good-first-issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
yunaremaia/taintrace#110 ·