OAuth2 "No input file specified": Page 2

OAuth2 "No input file specified"

KevinTheJedi

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.

apers

Thank you for the guidance but the previous steps became a bit too daunting for me. I think I have discovered the cause of the problem. The osticket database had been imported from another osticket instance causing the looping issue. I had moved back over to another Win 11\IIS osticket instance that was working fine. Once I imported the osticket DB from a Win 10 \ IIS instance I had the same problem with the oauth2 creating a looping effect when submitting. Is there a way I could simply import the tickets from my current production osticket running Windows 10 / IIS cleanly?

KevinTheJedi

apers

If you go through the normal migration and upgrade procedures you will never run into such issues. How are you dumping the data on the old server and importing it into the new one? Is the URL the same? If not that makes a big difference.

To answer your question it'd be hell trying to map partial data like that. You either do all or nothing and as I said above if you do everything correctly you will not have such issues.

Cheers.

apers

I will need to verify with my coworker but I am pretty sure he just imported the entire database onto the new ticketing system through MySQL Workbench. Maybe using the migration wizard. The URL is different since it is based on the hostname of the computer. Maybe I could just change the hostname of that computer to the old ticketing system and be set?

I will review the upgrade and migration procedures.

Thank you.

KevinTheJedi

apers

Well if the URL is different then that would be why.. You can read my comment below on how to properly migrate/upgrade your data:

https://forum.osticket.com/d/106585-trouble-exporting-tickets/4

After your've migrated and upgraded the data on the new server go to Admin Panel > Settings > System, update the Helpdesk URL to what it actually is, and Save Changes. Then you must go to your App Registration in Entra ID and update the "Redirect URIs" section to add your new URL. Now, you must go back to osTicket and to each email you are configuring OAuth2 for, manually update each Redirect URI to match your new URL (just the base of it - the /api/auth/oauth2 bit stays put), click Save, reauthorize each email, and retest.

Cheers.

apers

https://forum.osticket.com/d/106585-trouble-exporting-tickets/4

Creating the new database and importing our SQL file (refereneced in the hyperlink above) from the old database resolved the issue for us. Previously we had just imported the entire old database which seemed to cause that looping issue when submitting the Azure app from the Oauth2 plugin.

KevinTheJedi

apers

That’s so wild lol At least it resolved your issues!

Cheers.

apers

As always thank you once again!

« Previous Page