Allow to set administrator email on installation

Given the security perspective, I think this is a better title.

A concerted effort was made to minimize the number of questions asked by the installer. If we’re gonna do this, it needs to be signed off on by the UX team.

Assigning to @ckrina to weigh in.

When WASM was the main testing tool, we decided we'd remove the step to set the user email and password to reduce the number of screens, as Adam says. But since that won't be the testing tool and there might be other reasons to ask for the email, I doubt we'll skip this step in the foreseeable future. Assigning to @pameela to validate this issue can be closed.

This blocks #3491190-7: [PP-1] Style installer with updated designs → , which it itself a stable blocker. Therefore, this is now a critical stable blocker. Assigning to myself to work on it, since collecting credentials when the system is not installed has security implications.

phenaproxima → credited rikki_iki → .

This took some fairly heavy refactoring in the installer but it works, using the form copied from 📌 Style installer with updated designs. Active (adding credit for that).

I would like this reviewed from a security perspective -- it stores the provided email and password in cleartext in a temporary file, which is the only place I could think of to store persistent data in the early (pre-database) installer. The only other option I'm aware of is the URL, which is natively supported by the core install system, but also a total non-starter for obvious reasons.

The file is:

• Outside the web root
• Deleted at the end of the installation (if it can't be deleted, it throws an exception and explicitly calls it out as a security risk)

I'll probably have to adjust the tests a bit but this is ready for review. I'm sending it directly to @tim.plunkett since this involves persisting sensitive data to a place where it could potentially be seen by unexpected eyes.

phenaproxima → changed the visibility of the branch 3489375-installer-credentials to hidden.

phenaproxima → closed merge request !261

After all that, it turns out that a little task juggling and a form alter hook will satisfy all comers. This is no longer iffy from a security perspective; it's rock solid. Assigning to Pam for a quick manual test.

Looks good to me.

Great. Self-assigning to deal with legitimate test failures, then I'll merge it.

OK, I think that gives us a big leg up towards getting 📌 Style installer with updated designs. Active done. Merged into 0.x!

Crediting @poker10 for reporting this.

Automatically closed - issue fixed for 2 weeks with no activity.