OAuth2 "No input file specified"

apers

osTicket Version v1.17.6 (3ff35ad)
Web Server Software Apache/2.4.62 (Win64) OpenSSL/3.0.15 mod_fcgid/2.3.10-dev
MySQL Version 8.4.3
PHP Version 8.1.0
Mail Fetching/Receiving: IMAP
OS: Windows 11

I am getting a "No input file specified" error when submitting the request to configure oauth2. I have done this before successfully with IIS but I am using Laragon with Apache and I am unable to get past this error.
I made sure URL rewriting is enabled and made various changes to the httpd.conf file but I continue to get the same error. I am using a client ID and secret from another ticketing system that I have removed the token on. The redirect URL is http://localhost/osTicket/api/auth/oauth2 so I figure I can apply it to another computer.

Here is the entry I have to my httpd.conf file. I figure the problem might be somewhere with this file.

</Directory>
<Directory /www/osticket>
Options Indexes FollowSymLinks MultiViews
AllowOverride All
Require all granted
</Directory>

KevinTheJedi

apers

Looks fine to me. That error simply means url rewriting is not allowed or is being blocked or something. Some people have success by modifying the api/.htaccess file and updating the [L] to [R,L]. Make sure you reload Apache and PHP-FPM is you’re running it.

Cheers.

apers

I did try updating the [L] to [R,L] in the api/.htaccess file. But once I input the Microsoft email credentials I am redirected to localhost/osTicket/. Could there be another issue with the api/.htaccess or httpd.conf file?

Any suggestions on how to troubleshoot if URL rewriting is functioning correctly?

KevinTheJedi

apers

No, that likely means there is an underlying error so it redirects to the homepage. You can modify your bootstrap.php file and set display_errors and display_setup_errors to 1 and retest to see if it outputs an error on screen.

Cheers.

apers

KevinTheJedi

It looks like that is already set by default. This is what I get have from the bootstrap.php file -

    #Don't display errors
    ini_set('display_errors', '1'); // Set by installer
    ini_set('display_startup_errors', '1'); // Set by installer

Is there a file that would log any errors?

KevinTheJedi

apers

Many different ones but sometimes none; welcome to the world of debugging lol Typical logs are PHP error logs and Apache error logs but could be a number of different logs depending on where the issue lies.

Cheers.

KevinTheJedi

apers

Post a screenshot of your email's oauth2 config information (censoring any sensitive information).

Cheers.

apers

KevinTheJedi

I had already checked the PHP and Apache error logs but nothing was being added at the time I tried to submit the plug in.

apers

KevinTheJedi

apers

Are your endpoints really the "common" ones? Those are just the defaults we ship with that you are supposed replace with your real endpoints. You may be using the "common" ones but you need to verify to ensure that. Go to the app registration in azure, go to Overview tab, click on Endpoints button at the top, and look for the OAuth2 (v2) endpoints. Then compare them to see if they differ from the "common" ones. If so, update your endpoints in osTicket and retest.

Cheers.

KevinTheJedi

apers

The url contains the secret all along. If you read it it says the app is not configured as a multi-tenant application and cannot use the common endpoints. So my above response still stands true. You need to get the real endpoints and update them in osTicket.

Cheers.

apers

Sorry. Disregard the screenshot. I must have had set the default endpoints during my troubleshooting by mistake. I just applied the correct endpoints but get the same 'No input file specified' error.

KevinTheJedi

apers

If you've already made the change to the api/.htaccess file of adding [R,L] then that error means one of three things:

URL Rewrite module is not installed or enabled in your Apache instance. Google the correct command to check that for your specific OS.
The URL Rewrite module may be installed and enabled but URL Rewriting is not enabled for the site. See the example below of a proper <Directory> block that allows URL rewrites.
The URL is returning like your earlier (now deleted) post with some bull-crap tacked on to it. A proper redirect should look like: https://domain.tld/api/auth/oauth2?code=xxx&state=xxx&session_state=xxx

Apache Site Config Example

Note: This is obviously an example. Your config may look different - the patch will definitely be different.

<Directory "/var/www/your_site_root/">
    Options Indexes FollowSymLinks
    AllowOverride All
    Require all granted
</Directory>

Cheers.