✎ appnotes:authmenus - Etherboot/gPXE Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

====== User-specific boot menus ======

This page outlines the steps I took to implement a proof of concept comprising user authentication at preboot time and dynamically generated boot menus.  The user is first presented with a login screen.  The user's credentials are passed via an SSL-encrypted link to a server, which authenticates the user and then provides a boot menu containing a list of authorised boot selections.  The list of boot selections can vary according to the user.

===== Setup =====

Find a suitable Apache web server, complete with valid SSL certificate.  Create a directory called "boot" on this web server.  For the purpose of this documentation, I will assume that the full URI for this directory is //%%http://my.web.server/boot%%//.

In the boot directory, create a file ".htaccess" containing

    SSLRequireSSL

and a file "menu.gpxe" containing

    #!gpxe
    
    imgfree
    login
    kernel -n menu https://${username:uristring}:${password:uristring}@my.web.server/boot/vesamenu.c32 menu.php
    boot menu

Trace: • qemu • journal • week2 • autobootchainurl • ibft • httpboot • yazzy • sanboot • winbootibft • probsbkoromomatic • project_plan • start • romomaticbko • todo • romburning • 2009 • commandline • soc • journal • 2010