improvements to flow when logging in to edit

[ghwood]

Currently, when a not-logged-in-to-Datatracker visitor is on an arbitrary IETF wiki page (e.g. https://wiki.ietf.org/group/emodir), and uses the Edit button to begin editing, they are directed to a page indicating they are Unauthorized with a link to "login as".

When they press that link, they are prompted to log in via Datatracker and after completing that, returned to the "main" wiki page (in this example, https://wiki.ietf.org/).

Two things would make this friendlier:

a) providing some indication in the Unauthorized page that they will be using IETF Datatracker credentials when continuing via "Login as..", and

b) after completing the login process, returning the user to the page from which the edit request was made.

[justinacolmena]

Somewhere between Sam Brinton, Sheriff Lamb, the DoD, the NSA, and a large number of recently fired CIA and FBI agents, there's an authentication issue or something with "IETF Datatracker credentials" -- if that's the authentication mechanism in use, then that's what's being used. And why the fork of the whole wiki.js project? But anyways, on to 3.0 if that is the plan.

Yes. I agree with point (b) but point (a) is merely a minor custom site modification.

I hate to change the subject, maybe it is on topic with authentication, but I half suspect there's a military shop doing fact-checking online and running a "Q Drop" to purge "misinformation" from private databases and pages are disappearing. That's a "DELETE FROM" not a "DROP TABLE" though, w.r.t. PostgreSQL, it is reputedly very stable solid and reliable, but beware people who "have been in business too long" and there is old code that isn't up to snuff in all modern situations especially if you are doing something other people do not want you to do, and certainly on a wiki, where it is tempting for others to attempt a defacement when they do not have the necessary permissions or authorization.