emergency access problems
Hi I appear to be having difficulty logging into the ZMI using the password created on install. I did change some settings to my root login using the Samplex member product etc but didn't change the password, login etc. Anyway I've followed all the instructions in security.txt, telnetting in as the user that made the zopeinstance and running python zpasswd.py access using SHA-1 and then entering nothing for domains ( I presumed that this would give access for all domains etc) I then get an access denied message on running this and the access file is not created. Any help would be appreciated. I guess I can always create a new zope instance and delete the old one?
Just to say that I solved this by using ./zopectl adduser <name> <password> with zope shut down. On 9/29/05, michael nt milne <michael.milne@gmail.com> wrote:
Hi I appear to be having difficulty logging into the ZMI using the password created on install. I did change some settings to my root login using the Samplex member product etc but didn't change the password, login etc. Anyway I've followed all the instructions in security.txt, telnetting in as the user that made the zopeinstance and running python zpasswd.py access using SHA-1 and then entering nothing for domains ( I presumed that this would give access for all domains etc) I then get an access denied message on running this and the access file is not created. Any help would be appreciated. I guess I can always create a new zope instance and delete the old one?
michael nt milne wrote:
Hi
I appear to be having difficulty logging into the ZMI using the password created on install. I did change some settings to my root login using the Samplex member product etc but didn't change the password, login etc.
Anyway I've followed all the instructions in security.txt, telnetting in as the user that made the zopeinstance and running
python zpasswd.py access
using SHA-1 and then entering nothing for domains ( I presumed that this would give access for all domains etc)
I then get an access denied message on running this and the access file is not created.
Any help would be appreciated. I guess I can always create a new zope instance and delete the old one?
You must make sure the access file is in the right place (an instance home, I believe) and you have to restart for it to take effect. --jcc -- "Building Websites with Plone" http://plonebook.packtpub.com/ Enfold Systems, LLC http://www.enfoldsystems.com
Yes, the access file was being created in the homeinstance. One thing I didn't do was run the zpasswd.py file when zope was stopped though, as I did with ./zopectl On 9/29/05, J Cameron Cooper <zope-l@jcameroncooper.com> wrote:
michael nt milne wrote:
Hi
I appear to be having difficulty logging into the ZMI using the password created on install. I did change some settings to my root login using the Samplex member product etc but didn't change the password, login etc.
Anyway I've followed all the instructions in security.txt, telnetting in as the user that made the zopeinstance and running
python zpasswd.py access
using SHA-1 and then entering nothing for domains ( I presumed that this would give access for all domains etc)
I then get an access denied message on running this and the access file is not created.
Any help would be appreciated. I guess I can always create a new zope instance and delete the old one?
You must make sure the access file is in the right place (an instance home, I believe) and you have to restart for it to take effect.
--jcc -- "Building Websites with Plone" http://plonebook.packtpub.com/
Enfold Systems, LLC http://www.enfoldsystems.com
michael nt milne wrote:
Anyway I've followed all the instructions in security.txt, telnetting
stop right there... you should be using ssh...
in as the user that made the zopeinstance and running python zpasswd.py access using SHA-1 and then entering nothing for domains ( I presumed that this would give access for all domains etc)
correct.
I then get an access denied message on running this and the access file is not created.
well, maybe you could show us the error rather than not quite giving us enough information to be able to help you ;-) guesses: - your user didn't have permission to read or maybe execute python or zpasswd.py - your user didn't have permissions to write to the directory where you were trying to create the access file.
Yes, the access file was being created in the homeinstance.
But yet you said above it wasn't created a all?!
One thing I didn't do was run the zpasswd.py file when zope was stopped though, as I did with ./zopectl
zope doesn't need to be stopped, but it does need to be restarted once the access file has been created... that said, if you want zopectl to let you do things without stopping Zope, just get a ZEO setup up and running... cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
Thanks. I sorted it out using ./zopectl adduser. On 9/30/05, Chris Withers <chris@simplistix.co.uk> wrote:
michael nt milne wrote:
Anyway I've followed all the instructions in security.txt, telnetting
stop right there... you should be using ssh...
in as the user that made the zopeinstance and running python zpasswd.py access using SHA-1 and then entering nothing for domains ( I presumed that this would give access for all domains etc)
correct.
I then get an access denied message on running this and the access file is not created.
well, maybe you could show us the error rather than not quite giving us enough information to be able to help you ;-)
guesses:
- your user didn't have permission to read or maybe execute python or zpasswd.py
- your user didn't have permissions to write to the directory where you were trying to create the access file.
Yes, the access file was being created in the homeinstance.
But yet you said above it wasn't created a all?!
One thing I didn't do was run the zpasswd.py file when zope was stopped though, as I did with ./zopectl
zope doesn't need to be stopped, but it does need to be restarted once the access file has been created...
that said, if you want zopectl to let you do things without stopping Zope, just get a ZEO setup up and running...
cheers,
Chris
-- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
participants (3)
-
Chris Withers -
J Cameron Cooper -
michael nt milne