No permissions as admin

inno · Post by **inno** » 21 Oct 2008, 02:33

Sorry I post this in English but I don't speak German.

I installed OTRS and the required Perl modules on a FC6 Linux system. Everything went fine.

After I configured OTRS (adding queues, system configurations, adding customers, ...) I logged in as customer via customer.pl to see how this part of OTRS looks like.

When I logged in again as admin via index.pl I lost all my administrator priviliges. Although I have the "Don't work with UserID 1 (System account)! Create new users! " on top of the page as legend of the icon I can't access the admin pages: "No Permission to use this frontend module!". Also the admin buttons are missing. Please see the screenshot in attachment. Typing index.pl?Action=Admin gives a permission error as well.

I checked the valid_id in the user table and it's still 1.

The version of OTRS is 2.3.3 .

Can somebody please give a solution for this.

Thanks,

Inno

Dizzy · Post by **Dizzy** » 21 Oct 2008, 07:52

Did you try executing script $OTRS_HOME/bin/SetPermissions.sh ?
Use that with
SetPermissions.sh <OTRS_HOME> <OTRS_USER> <WEBSERVER_USER> [OTRS_GROUP] [WEB_GROUP]

(I have installed OTRS on Suse 10.2 and was able to execute SetPermissions.sh /opt/otrs otrs wwwrun www www)

inno · Post by **inno** » 21 Oct 2008, 10:58

This has been done during the installation. I followed the instructions for the installation from the source. And it all went fine.

I executed SetPermissions.sh again, but it didn't give any difference. In my case the command is SetPermissions.sh /opt/otrs otrs apache nfsnobody apache.

Everything worked initialy. But something must have gone wrong while I configured OTRS using the web interface. When I logged out and logged in again, I didn't got the admin permissions anymore.

In the Kernel/System/Web/InterfaceAgent.pm I found this:

Code: Select all

            if ( !$Param{AccessRo} && !$Param{AccessRw} || !$Param{AccessRo} && $Param{AccessRw} ) {
                print $Self->{LayoutObject}->NoPermission(
                    Message => 'No Permission to use this frontend module!'
                );
                exit 0;
            }

So what might be changed so this condition returns true? The system doesn't recognise user 1 as admin anymore. Is the recognision based on the user ID only or is there an admin flag as well? Maybe the flag has been set to false accidentally. Or must the admin user be a member of a certain group?

Thanks,

Inno

inno · Post by **inno** » 21 Oct 2008, 11:36

I found what caused this:

I added groups with the first letter in uppercase. For estetical reasons I changed the group name 'admin' to 'Admin' (to have everything with a first capital letter). It seems that the group name is protected.

To summarize:

- A group with the lowercase name 'admin' has to exists
- User 1 has to be a valid member of this group

Strange that such advanced system allows you to change a protected name. Maybe this is something for on the wishlist of OTRS.

Thanks,

Inno