×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I have removed two users from all folders who are no longer authorized
to my IBM i. I disabled their user profiles and removed their authority
from all files and folders. When I attempt to edit a configuration
file using the GUI I get the following error:
*Error:* ZUI_50008: You do not have the necessary authority to update
configuration file */www/myapps/conf/httpd.conf*.
The myapps folder has the following authority:
*PUBLIC *X
PETE *RWX (and all object authorities)
QTMHHTTP *X (an no object authorities)
and the /www/myapps/conf folder has:
*PUBLIC *X
QSYS *RWX (and all object authorities)
PETE *RWX (and all object authorities)
QTMHHTTP *X (an no object authorities)
When I create a brand new HTTP server instance using the ADMIN GUI I see
the following:
*Error:* ZUI_50009: An unknown error occurred attempting to update
configuration file */www/testsec/conf/httpd.conf*.
The folders and files created by the GUI have the following permissions:
*PUBLIC *X
PETE *RWX (and all object authorities)
QTMHHTTP *X (an no object authorities)
I (PETE) have all authorities on the system.
Something was changed, perhaps by the user who had the original
authorities on the folders and has now been removed. I would have
thought that a "clean" creation of a new HTTP instance would have the
correct authorities (which I think would have QTMHHTTP with *RXW and all
authorities on all objects, correct?)
Where are the "controls" that determine what an HTTP instance has
regarding authority? How do I fix this (is it a user profile issue on
QTMHHTTP?)?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.