OAuth2 Plugin Redirect To Tickets.php

Owain

I'm using v1.18 (724de45).

When I login as a user with a username/password, once authenticated I get redirected to the /tickets.php page. I also have the Oath2 plugin configured to login with Google accounts, but when I use that method, once authenticated I end up back at the Support Center Home page. Is there a way to get this to redirect to the /tickets.php page also?

KevinTheJedi

Owain

You likely don’t have URL Rewriting enabled on your webserver. You need to enable URL Rewriting on your webserver, restart the webserver, and retest. You may even need to edit your main Apache config for the site with the site directory and add AllowOveride All (there are guides online that explain this).

If that doesn’t work then you likely have something misconfigured; either in the Google Project or in the OAuth2 settings in osTicket.

Cheers.

Owain

KevinTheJedi
I'm actually using nginx, which I understand isn't supported, but since the redirect user/pass login method is working then the OAth2 method should also be working? I went through the config for the plugin and the instance again and can't find an issue anywhere. Its loging users in fine, it just doesn't end up on the correct page after login.

KevinTheJedi

Owain

No, OAuth2 uses API endpoints for auth and normal login uses local PHP file.

You are correct, NGINX is not supported and why you are having this issue. The best thing is to switch to Apache or LiteSpeed as those are supported out of the box. If you have to stick with NGINX then you can search older posts for the right NGINX config to use.

Cheers.

Owain

KevinTheJedi
Yeah, I have to stick with Nginx as there are other things running on this server that require it.

Is there something on the index.php page to check to see if the login is valid then redirect to tickets.php?

KevinTheJedi

Owain

As mentioned above if you need NGINX then you must look at resources online for the correct NGINX rules to use. Here is an example:

https://github.com/osTicket/osTicket/issues/6293#issuecomment-1315838614

Cheers.