HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Apache Authorization Realms
Operating System - Linux
1832890
Members
2007
Online
110048
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-01-2003 02:38 PM
08-01-2003 02:38 PM
Apache Authorization Realms
Hello,
I'm trying to configure apache Apache so that each virtual host that I have will have a seperate realm with one authorized user.
It's for allowing an admin of each site to view a statistics page.
So I want only that user to be able to view the stats for their site.
I'm pretty sure I can do this by defining seperate blocks, one for each virtual host, and define in it a seperate realm and give access to only one user.
And of course create those users with htpasswd.
Something like this maybe
AllowOverride AuthConfig
AuthType Basic
AuthName "Stats Page"
AuthUserFile /etc/httpd/users
Require user domain1user
AuthType Basic
AuthName "Stats Page"
AuthUserFile /etc/httpd/users
Require user domain2user
But is there a more concise way to do this?
Is there a way to use the normal Linux user accounts for authorization?
Or some other way which wouldn't require a new Directory block for each site?
Thanks...
-Travis
I'm trying to configure apache Apache so that each virtual host that I have will have a seperate realm with one authorized user.
It's for allowing an admin of each site to view a statistics page.
So I want only that user to be able to view the stats for their site.
I'm pretty sure I can do this by defining seperate
And of course create those users with htpasswd.
Something like this maybe
AllowOverride AuthConfig
AuthType Basic
AuthName "Stats Page"
AuthUserFile /etc/httpd/users
Require user domain1user
AuthType Basic
AuthName "Stats Page"
AuthUserFile /etc/httpd/users
Require user domain2user
But is there a more concise way to do this?
Is there a way to use the normal Linux user accounts for authorization?
Or some other way which wouldn't require a new Directory block for each site?
Thanks...
-Travis
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-01-2003 03:35 PM
08-01-2003 03:35 PM
Re: Apache Authorization Realms
I am pretty experienced with apache and can not think of a way to do this more efficiently.
If you just use linux accounts and permissions, I don't think apache will work right. You'd just get a forbidden 403 error.
Are their efficiency issues here? Is this burning up the cpu?
There is an old rule with apache once you get it to do what you want. If it works, don't try and fix it.
SEP
If you just use linux accounts and permissions, I don't think apache will work right. You'd just get a forbidden 403 error.
Are their efficiency issues here? Is this burning up the cpu?
There is an old rule with apache once you get it to do what you want. If it works, don't try and fix it.
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-01-2003 03:58 PM
08-01-2003 03:58 PM
Re: Apache Authorization Realms
Okay, is what I described pretty much the standard way to do something like this?
There is no resource issues, I was just wondering if there was a more general way that I could do this, more automated.
Thank you...
-Travis
There is no resource issues, I was just wondering if there was a more general way that I could do this, more automated.
Thank you...
-Travis
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-01-2003 11:16 PM
08-01-2003 11:16 PM
Re: Apache Authorization Realms
To automate the process you could have a backend (database, file, whatever) and a script (bash, perl, awk, python, you name it) that generates the virtual host part.
Say you create a virtualhosts file. You then use the include directive to make it part of the httpd.conf config file.
Now to add a new host you would add it in the backend, rerun the virtualhosts script and restart apache. (or hup it to reload it's config, i don't know if possible).
Next you can write a web interface on top of the backend to make administration easier.
That should be automated enough.
Cheers
Cristi
PS There's someone who sells a commercial Apache configuration interface that does web-based apache configurations. Or you could look into webmin and other administration tools to see if the include virtual hosts configuration.
Say you create a virtualhosts file. You then use the include directive to make it part of the httpd.conf config file.
Now to add a new host you would add it in the backend, rerun the virtualhosts script and restart apache. (or hup it to reload it's config, i don't know if possible).
Next you can write a web interface on top of the backend to make administration easier.
That should be automated enough.
Cheers
Cristi
PS There's someone who sells a commercial Apache configuration interface that does web-based apache configurations. Or you could look into webmin and other administration tools to see if the include virtual hosts configuration.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP