Call for Bikeshedding: remote auth at install time

Adam Williamson awilliam at
Sun Jun 9 00:59:52 UTC 2013

On Sun, 2013-06-09 at 09:24 +0930, Glen Turner wrote:
> Kickstart is fine for centrally managed devices. They've got experienced
> sysadmins who don't mind getting dirty with configuration files.
> The real kicker is people who manage their own device: not just BYOD
> but also part-time sysadmins who can't run the corporate distribution.
> These people can suck substantial time from deep support at the help desk.
> For those people there does needs to be an easy way for them to configure
> a network authenticating account. But there's no need for that to be
> in the installation dialogues. Considering that IT support might approach
> them well after installation and say "our policy is that machine
> authenticate against the Corporate Blah rather than have local
> authentication" there's a strong argument for being able to do this well
> away from installation.
> I'd also strongly encourage a design which makes it easy for a
> corporate-issued RPM to configure the authentication. For an example of
> something wonderful, NetworkManager has a one-file-per-ssid design so its
> easy for a RPM to drop in the configuration files for the corporate wireless.
> I'd really like a company to be able to have a set of noarch RPMS which put
> in place the minimum configuration for use within the organisation.

Thanks. Those are some good thoughts, but since I'm just the test
monkey, I'm on a strict focus: 'blocker or not blocker'. I'm sure the
devs working on remote auth configuration would be interested in your
thoughts, though!
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | adamwfedora

More information about the devel mailing list