Question: I'm currently generating documentation on one machine, and publishing it to a web server using the following commands in a script:

```
net use "\\someShare" PASSWORD /user:username
del /S /Q "\\someShare"
xcopy /E /Y Documentation\html\* "\\someShare\"

```

However, it feels like a really bad idea to have a password as plain text in the script, so I'm looking for alternatives to my current solution. Ideas?

I definitely would appreciate a solution that uses some kind of access control, as many different people should be allowed to publish their own documentation to the web server, but not mess with each other's docs.

Answer: 
I compared it with another setup we had on nginx; it seems the problem was due to the properties 

```
ssl_client_header = SSL_CLIENT_S_D
ssl_client_verify_header = SSL_CLIENT_VERIFY

```

present in master's puppet.conf. Commenting them out from there and leaving the configuration for them as it is in Nginx fixed the problem.
Is your rack `config.ru` owned by user/group puppet:puppet? From the Puppet Labs documentation: 

`Whatever you do, make sure your config.ru file is owned by the puppet user! Passenger will setuid to that user.` <http://projects.puppetlabs.com/projects/1/wiki/using_passenger>

Also, make sure that /etc/puppet and /var/lib/puppet are also owned by puppet:puppet as well.