newbie: superuser login authorization failed
Source of installation binaries: http://starship.python.net/crew/jrush/Zope/Zope232.html - rpm install with zserver rather than apache pcgi install (I am still trying the rpm installation vs tarball.) OS: RH7.0 Python: python-1.5.2-27 Browser: NCommunicator 4.77 Resources: 1. mailing list archive: I found a thread written by Darci and Chris - Darci was having the problem of loging in as superuser - but then seemed to resolve the problem by stopping and restarting zope - which I did ad naseum. 2. zopedocs 3. zope help I know it isn't the information in the access file because I ran 'python zpasswd.py -u superuser -p mynewpassword -d localhost' - nada - 'Authorization failed' I have tried using NN6 - no joy. a look at the authfailed page source shows: <!-- Traceback (innermost last): File /usr/lib/python1.5/site-packages/ZPublisher/Publish.py, line 223, in publish_module File /usr/lib/python1.5/site-packages/ZPublisher/Publish.py, line 187, in publish File /usr/lib/python1.5/site-packages/ZPublisher/Publish.py, line 162, in publish File /usr/lib/python1.5/site-packages/ZPublisher/BaseRequest.py, line 462, in traverse File /usr/lib/python1.5/site-packages/ZPublisher/HTTPResponse.py, line 588, in unauthorized Unauthorized: (see above) --> well - that went right over MY head! On the mailing list whenever anyone mentions having a problem with the rpm installation the response is try the tarball install. I really do not want to do that if I can avoid it so if there is anyone out there who can help me with this..please? TIA, Nicole -- ######################## Nicole Lallande nicole@nmlconsulting.com 760.753.6766 ########################
And upon Saturday of June 16, the illustrious Nicole Lallande spake thusly... <snip>
On the mailing list whenever anyone mentions having a problem with the rpm installation the response is try the tarball install. I really do not want to do that if I can avoid it so if there is anyone out there who can help me with this..please?
Dude -- just do the tarball... it's easy. Beers, Corey
On 17/6/01 12:58 am, "Nicole Lallande" <nicole@nmlconsulting.com> wrote:
Source of installation binaries: http://starship.python.net/crew/jrush/Zope/Zope232.html - rpm install with zserver rather than apache pcgi install (I am still trying the rpm installation vs tarball.)
Ok, I'll probably get battered for this, but people seem to have fewer problems with the tarball than with the RPM. Chris mentioned the linux binary release, and as someone who started off with binary releases (Solaris) I can state that they *do work*.
OS: RH7.0 Python: python-1.5.2-27 Browser: NCommunicator 4.77 Resources: 1. mailing list archive: I found a thread written by Darci and Chris - Darci was having the problem of loging in as superuser - but then seemed to resolve the problem by stopping and restarting zope - which I did ad naseum. 2. zopedocs 3. zope help
I know it isn't the information in the access file because I ran 'python zpasswd.py -u superuser -p mynewpassword -d localhost' - nada - 'Authorization failed' I have tried using NN6 - no joy.
I use this: % python zpasswd.py -u admin -p 'somerubbish' access (I note you haven't got a filename in the above zpasswd line). To create the access file (it can also be called 'inituser', I prefer access). Then, I do this (on a stock install) % ./start And get this [9:14pm tonymcd ~/software/Zope-2.3.3b1-src]% ./start ------ 2001-06-16T20:15:00 INFO(0) ZServer HTTP server started at Sat Jun 16 21:15:00 2001 Hostname: localhost Port: 8080 ------ 2001-06-16T20:15:00 INFO(0) ZServer FTP server started at Sat Jun 16 21:15:00 2001 Hostname: localhost Port: 8021
a look at the authfailed page source shows:
<!-- Traceback (innermost last): File /usr/lib/python1.5/site-packages/ZPublisher/Publish.py, line 223, in publish_module File /usr/lib/python1.5/site-packages/ZPublisher/Publish.py, line 187, in publish File /usr/lib/python1.5/site-packages/ZPublisher/Publish.py, line 162, in publish File /usr/lib/python1.5/site-packages/ZPublisher/BaseRequest.py, line 462, in traverse File /usr/lib/python1.5/site-packages/ZPublisher/HTTPResponse.py, line 588, in unauthorized Unauthorized: (see above)
-->
well - that went right over MY head!
It's a traceback - and yes to people new to Zope, it is daunting. What it's saying is that you're unauthorized for the URL you were trying to look at. Was it http://localhost:8080/manage ? 'cos that's the page most people want to get into after starting a Zope installation up.
On the mailing list whenever anyone mentions having a problem with the rpm installation the response is try the tarball install. I really do not want to do that if I can avoid it so if there is anyone out there who can help me with this..please?
TIA,
Nicole
There's the tarball source installation, and the tarball binary installation. The binary releases are only made for beta and final versions of Zope (that's why there's no binary for 2.4.0a1 - 'here be dragons!'). If your system has a python installation and a C compiler, installing from the source tarball boils down to this; % python wo_pcgi.py And then sit back and watch as things are compiled up before you. Later on, you might want to integrate with Apache, and so might do % python w_pcgi.py To enable the Persistent CGI machinery. But, threads on the list recently (VirtualHostMonsters and Apache) have convinced me to nuke all our CGI machinery and use Zserver (which is what is actually sitting on port 8080) instead. That is, you may not *need* to do the % python w_pcgi.py dance. What I would suggest is 1) D/L the binary tarball for Linux x-86 2) Follow those instructions and you *will* be up and running in no time Or if you have a working python 1.5.2 and C compiler 1) D/L the source tarball for 2.3.2 and 2) % python wo_pcgi.py There's a lot of information to assimilate when first using Zope Nicole, not least the different publishing model the system uses. It's definitely worth it - we have about a dozen developers thundering away at Zope now and our productivity is dramatically higher than the old Perl/PHP days... HTH Tone -- Dr Tony McDonald, Assistant Director, FMCC, http://www.fmcc.org.uk/ The Medical School, Newcastle University Tel: +44 191 243 6140 A Zope list for UK HE/FE http://www.fmcc.org.uk/mailman/listinfo/zope
Tony McDonald wrote:
Ok, I'll probably get battered for this, but people seem to have fewer problems with the tarball than with the RPM. Chris mentioned the linux binary release, and as someone who started off with binary releases (Solaris) I can state that they *do work*.
I try to use RPM installations most of the time because I am a 'sunday programmer' and tarball installations tend to require more of my input - but at this point I give up on the rpms both the powertools version and the zope list version - been down those roads for 2 days now with no success.
(I note you haven't got a filename in the above zpasswd line).
I had it in there - I have successfully added and changed passwords in this file but it is still not recognized - I sure hope I don't get through the tarbal install and find that the problem is with NN4.77 - please tell me that is NOT going to happen! I wonder about encoding - if the browser encodes the password using a different encoding method than it was created with in the access file - then how can they be matched? the zpasswd.py file mentions three different encoding options - SHA, UNIX and CLEARTEXT - the question is what is the browser using?
It's a traceback - and yes to people new to Zope, it is daunting. What it's saying is that you're unauthorized for the URL you were trying to look at. Was it
-yes - that's the url - glad to know that is all they are saying - too bad there is not a way to fix it.
There's the tarball source installation, and the tarball binary installation. The binary releases are only made for beta and final versions of Zope (that's why there's no binary for 2.4.0a1 - 'here be dragons!').
OK - now I do have a working python compiler - but why would I want to do the source install if I have the binaries? is there any benefit of doing the source installation vs the other? Also thanks for your advice on the Zserver vs apache configuration - something I read somewhere (the book, the docs, the help, the mailing list archive -- <scotty beam me UP>) in the past two days convinced me to use the Zserver configuration. Are you saying that out of the tarball 'box' so to speak the configuration is Zserver? or do I have to do something special to select zserver. is the zope start-up script placed into the /etc/rd.d/init.d directory on this install as well?
There's a lot of information to assimilate when first using Zope Nicole, not least the different publishing model the system uses. It's definitely worth it - we have about a dozen developers thundering away at Zope now and our productivity is dramatically higher than the old Perl/PHP days...
I am learning Zope for a client that is considering zope for their corporate intranet - seems like it would be perfect for that - I will also be very interested to see how it increases productivity in perl/php development (languages of choice for 'sunday' programmer such as myself.)
HTH Tone
Yes, TH'ed - thanks, Tone. Warm regards from San Diego, Nicole PS - almost went to England for a visit this month - got cancelled <sigh> -- ######################## Nicole Lallande nicole@nmlconsulting.com 760.753.6766 ########################
On 17/6/01 4:23 pm, "Nicole Lallande" <nicole@nmlconsulting.com> wrote:
I try to use RPM installations most of the time because I am a 'sunday programmer' and tarball installations tend to require more of my input - but at this point I give up on the rpms both the powertools version and the zope list version - been down those roads for 2 days now with no success.
Yes, I know where you're coming from - I tried the RPM stuff on my LinuxPPC box and it was neat, but as there weren't all that many RPMs for LinuxPPC, I ended up having to do the 'source code shuffle' anyhow! :)
(I note you haven't got a filename in the above zpasswd line).
I had it in there - I have successfully added and changed passwords in this file but it is still not recognized - I sure hope I don't get through the tarbal install and find that the problem is with NN4.77 - please tell me that is NOT going to happen! I wonder about encoding - if the browser encodes the password using a different encoding method than it was created with in the access file - then how can they be matched? the zpasswd.py file mentions three different encoding options - SHA, UNIX and CLEARTEXT - the question is what is the browser using?
Good point - I'm not sure. What I tend to do is edit the first line in the access or inituser file, which is probably showing; admin:{SHA}efba6152febsfa (I think) And edit it so's it says this admin:abc123 Ie the password is being sent in the clear. This is generally a baad thing, but you can set things up (again using those VirtualHostMonsters - VHM - and Apache), so that any management URLs are sent using https if you want to.
OK - now I do have a working python compiler - but why would I want to do the source install if I have the binaries? is there any benefit of doing the source installation vs the other?
In general I would have said no. However, if you have a working Python installation and you have (say) MySQL adaptors and PDF generators and the like installed within that python installation, your Zope installation gets all this for free (within External Methods - but let's not go there *just* yet).
Also thanks for your advice on the Zserver vs apache configuration - something I read somewhere (the book, the docs, the help, the mailing list archive -- <scotty beam me UP>) in the past two days convinced me to use the Zserver configuration.
It's the quickest thing to do to get a Zope installation up, and like I said in my last email, if you use Apache as well, you can integrate it very easily using VHM).
Are you saying that out of the tarball 'box' so to speak the configuration is Zserver?
Yes, using the % python wo_pcgi.py Installation setup.
or do I have to do something special to select zserver. is the zope start-up script placed into the /etc/rd.d/init.d directory on this install as well?
There's no special script supplied with the source distribution that goes into the /etc/init.d area, I think that's because it's not to easy to do this for all the platforms that Zope runs on. Someone wrote up a HOWTO on the Zope site that gives a clue how to do this for some unixes.
I am learning Zope for a client that is considering zope for their corporate intranet - seems like it would be perfect for that - I will also be very interested to see how it increases productivity in perl/php development (languages of choice for 'sunday' programmer such as myself.)
I think you're probably right. The permissions and security machinery in Zope is extremely flexible, and the CMF is certainly something to consider for an intranet. Zope isn't a language as such however, it's as the 'OPE' part of its name suggests, an 'Object Publishing Environment'.
Warm regards from San Diego,
Nicole
PS - almost went to England for a visit this month - got cancelled <sigh>
You certainly don't want to come here at the moment - it's very very wet! (eg check out the pictures from the 'trooping the colour' ceremony yesterday at http://news.bbc.co.uk/hi/english/uk/newsid_1392000/1392006.stm). Tone -- Dr Tony McDonald, Assistant Director, FMCC, http://www.fmcc.org.uk/ The Medical School, Newcastle University Tel: +44 191 243 6140 A Zope list for UK HE/FE http://www.fmcc.org.uk/mailman/listinfo/zope
the zpasswd.py file mentions three different encoding options - SHA, UNIX and CLEARTEXT - the question is what is the browser using? admin:abc123
Ie the password is being sent in the clear.
If I understand it correctly, the encoding option only applies to the access file. Authentication 'on the wire' uses HTTP Basic Authentication, so the password is allways sent in plain text.
There's no special script supplied with the source distribution that goes into the /etc/init.d area
Well, it's allways possible to use the script from the RPM of course. It's amazing to see the trouble it goes through just to start and stop the server :-) Regards, Rene Pijlman
participants (4)
-
coreyï¼ axcelerant.com -
Nicole Lallande -
Rene Pijlman -
Tony McDonald