Admin Problems after upgrade from 2.4.7 to 3.0.2

[piperdown]

Hope someone can help with this. Just upgraded, and after following the upgrade guide, seemed to go well.

Until I needed to use some of the admin functions, such as edit responses, links between agents and groups, agents and roles, and some other stuff.

I get the following in the httpd access logs

GET /otrs/index.pl?Action=AdminAutoResponse;Subaction=Change;ID=1 HTTP/1.1" 403 307

and a 403 forbidden

Forbidden

You don't have permission to access /otrs/index.pl on this server.

I've reviewed permissions, to no avail.

Running CentOS 5.4. Redirecting to https.

[Wolfgangf]

did you already run the following:

Code: Select all

11) Refresh the configuration cache and delete caches
    -------------------------------------------------

    Please run:

    shell> bin/otrs.RebuildConfig.pl
    shell> bin/otrs.DeleteCache.pl

[piperdown]

Yes... But will do it again.

Also rebuilt the Config.pm from Config.pm.dist, appending my changes (openldap auth for agents and customers).

I suspect a permissions issue either on the filesystem or the DB but so far cannot find anything.

[hmaurer]

Hi,

I've had the same problem recently. It looks like yours, i.e. some of tasks in Admin area cause the Error "403 Forbidden". For example, if I tried to open otrs/index.pl?Action=AdminRoleUser I got the list but the error, if I tried to open an item from the list. I investigated the problem and am sure that something between the web server (and OTRS) and the web browser doesn't allow the execution of the tasks.

In my case the problem caused by mod_security which runs on the reverse proxy. I can imagine that other security tools (WAF) could cause the problem too.

I hope I could help you.

Regards,
Hermann Maurer