1. 29 Oct, 2014 1 commit
  2. 28 Oct, 2014 1 commit
  3. 27 Oct, 2014 1 commit
  4. 25 Oct, 2014 2 commits
  5. 20 Oct, 2014 1 commit
  6. 17 Oct, 2014 3 commits
  7. 08 Oct, 2014 1 commit
  8. 25 Sep, 2014 1 commit
  9. 24 Sep, 2014 2 commits
  10. 18 Sep, 2014 2 commits
  11. 15 Sep, 2014 1 commit
    • Leigh Stoller's avatar
      Change to ssh key handling for registered APT/Cloud users; show the ssh key · 1822694e
      Leigh Stoller authored
      box, but as a collapsible. Warn user if they do not have a key (provided on
      signup page) that they are restricted to browser shell. Whenever user
      provides a key, replace in the database (if its changed). This keeps the
      user out of the Emulab interface to edit their ssh keys. Might have to
      revisit this if APT/Cloud users need/want more then the one key.
      1822694e
  12. 09 Sep, 2014 1 commit
  13. 08 Sep, 2014 1 commit
  14. 03 Sep, 2014 1 commit
  15. 02 Sep, 2014 1 commit
  16. 27 Aug, 2014 1 commit
    • Leigh Stoller's avatar
      Large set of changes for using the Geni trusted signer tool, to · 980f6cbd
      Leigh Stoller authored
      authenticate Geni users to CloudLab (who do not have Emulab accounts).
      CloudLab users must have an account to do anything (unlike APT which allows
      guest users). But instead of requiring them to go through the Emulab
      account creation (high bar), let then use their Geni credentials to prove
      who they are. We then build a local account for that new user, and save off
      the speaksfor credential so that we can act on their behalf when talking to
      the backend clusters (and their MA to get their ssh keys).
      
      These users do not have a local account password, so they cannot log into
      the web interface using the Emulab login page, nor do they have a shell on
      ops.
      
      Once authenticated, we put the appropriate cookies into the browser via
      javascript, so they can use the Cloud (okay, APT) web interface (they
      appear logged in).
      
      I make use of the nonlocal_id field of the users table, which was not being
      used for anything else. Officially, these are "nonlocal" users in the code
      (IsNonLocal()).
      
      When a nonlocal user instantiates a profile, we use their speaksfor
      credential to ask their home MA for their ssh keys, which we then store in
      the DB, and then provide to the aggregate via the CreateSliver call.
      Note that no provision has been made for users who edit their profile and
      add keys; I am not currently expecting these users to stumble into the web
      interface (yet).
      980f6cbd
  17. 19 Aug, 2014 1 commit
  18. 11 Aug, 2014 1 commit
  19. 08 Aug, 2014 1 commit
  20. 05 Aug, 2014 1 commit
  21. 31 Jul, 2014 1 commit
  22. 28 Jul, 2014 2 commits
  23. 15 Jul, 2014 1 commit
  24. 12 Jul, 2014 1 commit
  25. 11 Jul, 2014 1 commit
  26. 08 Jul, 2014 1 commit
  27. 01 Jul, 2014 1 commit
  28. 19 Jun, 2014 2 commits
  29. 18 Jun, 2014 1 commit
  30. 17 Jun, 2014 1 commit
  31. 12 Jun, 2014 1 commit
    • Kirk Webb's avatar
      Update the use of realpath across all perl scripts · 3f167217
      Kirk Webb authored
      Change to use the realpath function in the 'Cwd' module instead of
      calling realpath via the shell.  The shell command varies in its
      reaction to a missing final path component.  On some platforms (Linux,
      FBSD10+) realpath reports an error if the final component doesn't exist
      on the filesystem.  On others (FBSD < 10), it does not report an error.
      
      The perl function from 'Cwd' emulates the same behavior as FBSD prior to
      version 10, which is the behavior the scripts expect.
      
      From here on out, instead of using `realpath`, do the following:
      
      use Cwd qw(realpath);
      ..
      ..
      my $realpath = realpath($somepath);
      3f167217
  32. 11 Jun, 2014 1 commit
  33. 10 Jun, 2014 1 commit