Project

General

Profile

Actions

Bug #907

closed

Foreman behind apache with userauth.

Added by shawn taaj over 13 years ago. Updated over 12 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

So I am using this apache config for foreman.

<VirtualHost *:80>
ServerName dashboard.server.com
ServerAlias dashboard
DocumentRoot /opt/foreman/public
RailsAutoDetect On
AddDefaultCharset UTF-8
Alias /certs /opt/foreman/public/certs.php

&lt;Directory /opt/foreman/public/&gt;
Options ExecCGI
AllowOverride None
AuthType Basic
AuthName "Dashboard Access"
AuthUserFile /opt/foreman/foreman.auth
Require valid-user
Options FollowSymLinks
AllowOverride All
Order allow,deny
allow from all
&lt;/Directory&gt;
&lt;/VirtualHost&gt;

When going to dashboard.server.com it requests for the user name and password, if you click cancel a bunch of times it will drop you into the public folder. Not sure if this is a apache issue or rails.


Related issues 2 (0 open2 closed)

Has duplicate Foreman - Bug #908: Foreman behind apache with userauth.Duplicate05/17/2011Actions
Has duplicate Foreman - Feature #1300: Foreman should support HTTP AuthentificationClosedRomain Vrignaud11/07/2011Actions
Actions #1

Updated by Ohad Levy over 13 years ago

  • Status changed from New to Feedback
  • Priority changed from High to Normal

any reason why you are not using the built in foreman authentication?

simply add to your foreman settings file

:login: true

Actions #2

Updated by Yun Zheng Hu almost 13 years ago

I fixed the Apache Auth using the Location directive instead of the Directory.

I have configured it as following:

<Directory /var/www/foreman-0.4/public>
    Order Deny,Allow
    Allow from all
</Directory>

<Location "/">
    SSLRequireSSL
    AuthType "Digest" 
    AuthName "Restricted Access" 
    AuthUserFile /etc/htdigest.users
    require valid-user
    Order allow,deny
    Satisfy any
</Location>

Problem is that the user authentication is not passed to foreman, so everything you do is still under the Admin user if you look in the foreman Audit logs.
Is it possible to pass the user authentication from the webserver to the foreman web application?

Actions #3

Updated by Benjamin Papillon over 12 years ago

The problem should be resolved with bug http://theforeman.org/issues/1300
It is available in 1.0 release (currently RC)

Actions #4

Updated by Ohad Levy over 12 years ago

  • Status changed from Feedback to Duplicate
Actions

Also available in: Atom PDF