No Google Group - help, need to password protect single directory in container
See original GitHub issueHello,
I have tried to follow the instructions and done numerous searches elsewhere but I just cannot get a password protected location code block to appear inside a vhost container config.
I don’t want to password protect the whole container, just a single directory running off the web server on the container.
e.g.
location /linux/ {
auth_basic "Restricted";
auth_basic_user_file /etc/nginx/htpasswd/linux;
}
I have managed to bind the password file shown above inside the container from the host filesystem but cannot get the VIRTUAL_HOST / docker-gen to generate the required code block!
Hope anyone can help.
Thanks,
Paully
Issue Analytics
- State:
- Created 2 years ago
- Comments:6
Top Results From Across the Web
Manage a user's security settings - Google Workspace Admin ...
Open user security settings · Sign in to your Google Admin console. · In the Admin console, go to Menu · In the...
Read more >Active Directory user account provisioning - Google Cloud
This article shows you how to set up user and group provisioning between Active Directory and your Cloud Identity or Google Workspace account...
Read more >Box Collaboration Guidelines | Information Security Office
If a business need requires that a sensitive file be shared with users outside of campus, Box allows end users to password-protect public...
Read more >Google Provisioning - Okta Documentation
Learn the recommended way to provision Google Workspace users to Okta using SAML or AD to provide users with seamless SSO.
Read more >How to Password Protect Your WordPress Site: Every Method
Learn how to password protect WordPress using four different methods. Password protect your entire site, posts, categories, or parts of ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Great, problem solved and I am closing this issue.
Hope it helps someone else.
Keep up the great work.
OK, I think I may have solved the ‘bad news’ problem.
I am not sure if this is technically correct but I added an extra proxy_pass line to the extra /etc/nginx/vhost.d/example.com file, like so…
So, from this…
To this…
…and now the password protection works and it shows me the correct page at the correct location.
Does that look alright to everyone?