Fletcher Cocquyt <fcocq...@stanford.edu> writes: > We are doing some proof of concept testing on AWS and I've compiled up > the lastest mod_webauth 4.5.5 on a test Amazon EC2 AMI instance (The EC2 > instance is fronted by a testec2.stanford.edu DNS record)
> Initial tests ( AuthType WebAuth Require valid-user ) work perfectly - > HTTP headers get set as expected. > Are there any security implications running mod_webauth this way? > Are there any other issues to be aware of? That should be fine. The Stanford WebAuth environment fully supports servers running on non-Stanford networks. The only piece that you will have to work around is that you may not be able to run wallet directly on the Amazon EC2 instance, so you may have to download the WebAuth keytab elsewhere locally and then copy it (securely) to the node at Amazon. -- Russ Allbery <ea...@windlord.stanford.edu> Technical Lead, ITS Infrastructure Delivery Group, Stanford University
