Forbidden 403 for OIDC exempt PHP scripts #984
Unanswered
rich-page-vtm
asked this question in
Q&A
Replies: 1 comment 1 reply
-
I have been able to get further on this issue, but I still believe there may be an issue. I found that if I remove the section under the /app /path/to/web_browser Directory definition with the FilesMatch section:
and move it to its own Location directive without a FilesMatch:
The OIDC exemption for php under /app/ are allowed as we expect. I'm wondering now if there's an issue with OIDC exemption when a FilesMatch directive is used? Running mod_auth_openidc 2.4.11.2. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I have a server using mod_auth_openidc for a particular web application, but some portions of that app need to be exempt from OIDC authentication.
I've had some success with OIDC exempt locations using the "AuthType None" directive, but I'm having trouble with some php scripts where the "AuthType None" directive doesn't seem to work. I'm getting "Forbidden 403" errors.
Here's my config:
If I try to run the app/php_scripts/script.php I get a 403 Forbidden.
Now, we have a FilesMatch clause there that is used when a .php is used, which runs the php through the app_php.fcgi wrapper. You can see that I tried to add the "AuthType none" directive to the FilesMatch section, but that doesn't seem to work.
Any ideas as to what I might have to do to make the PHP script run (without OIDC authentication)?
Note: if I use this config without mod_auth_openidc, the php runs.
Thanks for your help!
Beta Was this translation helpful? Give feedback.
All reactions