[Trac] Re: upgrade problems with login

2007-01-19 Thread Rick Bradshaw



Good news I ended up finding my problem. I had a stray Satisfy any in
a clause that didn't seem to matter in my older version of Apache2,
but it certainly causes issues in my new version. so between apache2
2.0.54-5sarge1 and apache2 2.0.55-4ubuntu2.1 something changed which
made this Satify any apply differently. 


so here was the fix:


   AllowOverride None
   Options ExecCGI -MultiViews +SymLinksIfOwnerMatch
   AddHandler cgi-script .cgi
   Order allow,deny
   Allow from all
   Satisfy any


remove the "Satisfy any"


   AllowOverride None
   Options ExecCGI -MultiViews +SymLinksIfOwnerMatch
   AddHandler cgi-script .cgi
   Order allow,deny
   Allow from all


and bam it worked.

Thanks for the help
Rick


Rick Bradshaw <[EMAIL PROTECTED]> writes:


I have an issue where I am trying to upgrade my trac install from a
debian-sarge install of trac 0.9.6 to an ubuntu-dapper with 0.10.3. I
will note that the new install basically mimics my old setup the only
difference is the name.

Here is the config on the working server. sarge with trac 0.9.6 and
apache2 2.0.54-5sarge1, and python 2.3

RewriteEngine on
RewriteRule ^/$ http://trac.mcs.anl.gov/projects
RewriteRule ^/projects/+$ /projects/index.html [L]
RewriteCond /www/trac.mcs.anl.gov/projects/$1 -d
RewriteRule ^/projects/(.*)(/?.*)   /projects/trac.cgi$2 
[S=1,E=TRAC_ENV:/www/trac.mcs.anl.gov/projects/$1]
RewriteRule ^/projects/(.*) /projects/index.html


  AllowOverride None
  Options ExecCGI -MultiViews +SymLinksIfOwnerMatch
  AddHandler cgi-script .cgi
  Order allow,deny
  Allow from all
  Satisfy any



  SSLRequireSSL
  AuthPAM_Enabled on
  AuthType Basic
  AuthName "secure area"
  Require valid-user



  SetHandler mod_python
  PythonHandler trac.web.modpython_frontend
  PythonOption TracEnvParentDir /www/trac.mcs.anl.gov/projects
  PythonOption TracUriRoot /projects  



Here is the config from the upgraded machine that isn't
working. Ubuntu dapper amd64, trac 0.10.3, apache2 2.0.55-4ubuntu2.1,
and python 2.4

RewriteEngine on
RewriteRule ^/$ http://trac2.mcs.anl.gov/projects
RewriteRule ^/projects/+$ /projects/index.html [L]
RewriteRule ^/projects/(.*)/login$
https://trac2.mcs.anl.gov/projects/$1/login [L]RewriteCond
/disks/www/trac.mcs.anl.gov/projects/$1 -d
RewriteRule ^/projects/(.*)(/?.*)   /projects/trac.cgi$2 
[S=1,E=TRAC_ENV:/disks/www/trac.mcs.anl.gov/projects/$1]
RewriteRule ^/projects/(.*) /projects/index.html


   AllowOverride None
   Options ExecCGI -MultiViews +SymLinksIfOwnerMatch
   AddHandler cgi-script .cgi
   Order allow,deny
   Allow from all



   AuthPAM_Enabled on
   AuthType Basic
   AuthName "secure area"
   Require valid-user



   SetHandler mod_python
   PythonHandler trac.web.modpython_frontend
   PythonOption TracEnvParentDir /disks/www/trac.mcs.anl.gov/projects
   PythonOption TracUriRoot /projects


I have already tested and proven that the "AuthPAM_Enabled on" works
properly as my svn repos and authz tools all work as normal. The
problem I am seeing is that when I click on the login link in my new
trac install I get an apache 500 error in my logs and the trac page
says.

"Authentication information not available. Please refer to the
installation documentation."

I am slowly heading towards my wits end. I am sure there is someone
out there who can show me the errors of my ways.

Thanks for the help.

Rick





--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---



[Trac] Re: upgrade problems with login

2007-01-19 Thread Rick Bradshaw



So I still have no luck finding my error. Is there anyway to enable
debugging information in trac to see what is actually happening when I
click on the "login" link? I turned on loggin for the trac project I
am testing with, but it just lists the same problem as the actual
webpage. 


is there any reasonable way to fire trac up in a python interpreter so
I can find out what is actually happening or in my case not happening?

Rick


Rick Bradshaw <[EMAIL PROTECTED]> writes:


I have an issue where I am trying to upgrade my trac install from a
debian-sarge install of trac 0.9.6 to an ubuntu-dapper with 0.10.3. I
will note that the new install basically mimics my old setup the only
difference is the name.

Here is the config on the working server. sarge with trac 0.9.6 and
apache2 2.0.54-5sarge1, and python 2.3

RewriteEngine on
RewriteRule ^/$ http://trac.mcs.anl.gov/projects
RewriteRule ^/projects/+$ /projects/index.html [L]
RewriteCond /www/trac.mcs.anl.gov/projects/$1 -d
RewriteRule ^/projects/(.*)(/?.*)   /projects/trac.cgi$2 
[S=1,E=TRAC_ENV:/www/trac.mcs.anl.gov/projects/$1]
RewriteRule ^/projects/(.*) /projects/index.html


  AllowOverride None
  Options ExecCGI -MultiViews +SymLinksIfOwnerMatch
  AddHandler cgi-script .cgi
  Order allow,deny
  Allow from all
  Satisfy any



  SSLRequireSSL
  AuthPAM_Enabled on
  AuthType Basic
  AuthName "secure area"
  Require valid-user



  SetHandler mod_python
  PythonHandler trac.web.modpython_frontend
  PythonOption TracEnvParentDir /www/trac.mcs.anl.gov/projects
  PythonOption TracUriRoot /projects  



Here is the config from the upgraded machine that isn't
working. Ubuntu dapper amd64, trac 0.10.3, apache2 2.0.55-4ubuntu2.1,
and python 2.4

RewriteEngine on
RewriteRule ^/$ http://trac2.mcs.anl.gov/projects
RewriteRule ^/projects/+$ /projects/index.html [L]
RewriteRule ^/projects/(.*)/login$
https://trac2.mcs.anl.gov/projects/$1/login [L]RewriteCond
/disks/www/trac.mcs.anl.gov/projects/$1 -d
RewriteRule ^/projects/(.*)(/?.*)   /projects/trac.cgi$2 
[S=1,E=TRAC_ENV:/disks/www/trac.mcs.anl.gov/projects/$1]
RewriteRule ^/projects/(.*) /projects/index.html


   AllowOverride None
   Options ExecCGI -MultiViews +SymLinksIfOwnerMatch
   AddHandler cgi-script .cgi
   Order allow,deny
   Allow from all



   AuthPAM_Enabled on
   AuthType Basic
   AuthName "secure area"
   Require valid-user



   SetHandler mod_python
   PythonHandler trac.web.modpython_frontend
   PythonOption TracEnvParentDir /disks/www/trac.mcs.anl.gov/projects
   PythonOption TracUriRoot /projects


I have already tested and proven that the "AuthPAM_Enabled on" works
properly as my svn repos and authz tools all work as normal. The
problem I am seeing is that when I click on the login link in my new
trac install I get an apache 500 error in my logs and the trac page
says.

"Authentication information not available. Please refer to the
installation documentation."

I am slowly heading towards my wits end. I am sure there is someone
out there who can show me the errors of my ways.

Thanks for the help.

Rick





--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---



[Trac] Re: upgrade problems with login

2007-01-18 Thread Rick Bradshaw


Dave,
   you are correct. I am trying to stick with http auth due to my
requirements to be able to use AuthPam, which fits in with our normal
authentification method. Does anyone know if I were to switch to this
AccountManager if it will allow me to use Pam authentification?

Rick

David Abrahams <[EMAIL PROTECTED]> writes:


Rick Bradshaw <[EMAIL PROTECTED]>
writes:


"Authentication information not available. Please refer to the
installation documentation."


I recently had a similar problem when attempting to move from an
HTTP-authenticated system to using the new AccountManager.  The fix
was that I had to disable the LoginModule as described here:

 http://trac-hacks.org/wiki/AccountManagerPlugin#LoginModule

However, it seems from your config that you're not trying to use HTML
forms authentication, so that advice may not apply to you.

--
Dave Abrahams
Boost Consulting
www.boost-consulting.com





--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---



[Trac] Re: upgrade problems with login

2007-01-18 Thread David Abrahams


Rick Bradshaw <[EMAIL PROTECTED]>
writes:


"Authentication information not available. Please refer to the
installation documentation."


I recently had a similar problem when attempting to move from an
HTTP-authenticated system to using the new AccountManager.  The fix
was that I had to disable the LoginModule as described here:

 http://trac-hacks.org/wiki/AccountManagerPlugin#LoginModule

However, it seems from your config that you're not trying to use HTML
forms authentication, so that advice may not apply to you.

--
Dave Abrahams
Boost Consulting
www.boost-consulting.com


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---



[Trac] Re: upgrade problems with login

2007-01-18 Thread Rick Bradshaw


Matt,
   I have tried with commenting out the rewrite rules and
still end up with the same 500 error. I have even tried without https
completely and I still end up in the same spot.
   I will admit this is quite the baffling problem, and there has
to be something very small or stupid that I am missing.

Thanks for the response
Rick

Matthew Gillen <[EMAIL PROTECTED]> writes:


Rick Bradshaw wrote:

Here is the config on the working server. sarge with trac 0.9.6 and
RewriteEngine on
RewriteRule ^/$ http://trac.mcs.anl.gov/projects
RewriteRule ^/projects/+$ /projects/index.html [L]
RewriteCond /www/trac.mcs.anl.gov/projects/$1 -d
RewriteRule ^/projects/(.*)(/?.*)   /projects/trac.cgi$2
[S=1,E=TRAC_ENV:/www/trac.mcs.anl.gov/projects/$1]
RewriteRule ^/projects/(.*) /projects/index.html

Here is the config from the upgraded machine that isn't
working. Ubuntu dapper amd64, trac 0.10.3, apache2 2.0.55-4ubuntu2.1,
and python 2.4

RewriteEngine on
RewriteRule ^/$ http://trac2.mcs.anl.gov/projects
RewriteRule ^/projects/+$ /projects/index.html [L]
RewriteRule ^/projects/(.*)/login$
https://trac2.mcs.anl.gov/projects/$1/login [L]RewriteCond
/disks/www/trac.mcs.anl.gov/projects/$1 -d
RewriteRule ^/projects/(.*)(/?.*)   /projects/trac.cgi$2
[S=1,E=TRAC_ENV:/disks/www/trac.mcs.anl.gov/projects/$1]
RewriteRule ^/projects/(.*) /projects/index.html
...

I have already tested and proven that the "AuthPAM_Enabled on" works
properly as my svn repos and authz tools all work as normal. The
problem I am seeing is that when I click on the login link in my new
trac install I get an apache 500 error in my logs and the trac page
says.

"Authentication information not available. Please refer to the
installation documentation."

I am slowly heading towards my wits end. I am sure there is someone
out there who can show me the errors of my ways.


Does it have to do with the "https" in the rewrite rules in the second case?

Matt




--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---



[Trac] Re: upgrade problems with login

2007-01-18 Thread Matthew Gillen


Rick Bradshaw wrote:

Here is the config on the working server. sarge with trac 0.9.6 and
RewriteEngine on
RewriteRule ^/$ http://trac.mcs.anl.gov/projects
RewriteRule ^/projects/+$ /projects/index.html [L]
RewriteCond /www/trac.mcs.anl.gov/projects/$1 -d
RewriteRule ^/projects/(.*)(/?.*)   /projects/trac.cgi$2
[S=1,E=TRAC_ENV:/www/trac.mcs.anl.gov/projects/$1]
RewriteRule ^/projects/(.*) /projects/index.html

Here is the config from the upgraded machine that isn't
working. Ubuntu dapper amd64, trac 0.10.3, apache2 2.0.55-4ubuntu2.1,
and python 2.4

RewriteEngine on
RewriteRule ^/$ http://trac2.mcs.anl.gov/projects
RewriteRule ^/projects/+$ /projects/index.html [L]
RewriteRule ^/projects/(.*)/login$
https://trac2.mcs.anl.gov/projects/$1/login [L]RewriteCond
/disks/www/trac.mcs.anl.gov/projects/$1 -d
RewriteRule ^/projects/(.*)(/?.*)   /projects/trac.cgi$2
[S=1,E=TRAC_ENV:/disks/www/trac.mcs.anl.gov/projects/$1]
RewriteRule ^/projects/(.*) /projects/index.html
...

I have already tested and proven that the "AuthPAM_Enabled on" works
properly as my svn repos and authz tools all work as normal. The
problem I am seeing is that when I click on the login link in my new
trac install I get an apache 500 error in my logs and the trac page
says.

"Authentication information not available. Please refer to the
installation documentation."

I am slowly heading towards my wits end. I am sure there is someone
out there who can show me the errors of my ways.


Does it have to do with the "https" in the rewrite rules in the second case?

Matt

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---