I did this test:
https://www.templatemonster.com/help/how-to-check-whether-mod_rewrite-is-enabled-on-server.html
And it caused the base folder to redirect to the php file in question, implying that it is indeed enabled.
This worked -> RewriteRule ^.*$ mod_rewrite.php
Hey Kevin,
No, just confirmed that mod_rewrite is enabled and works but the issue with osTicket remains.
Did you make sure your Redirect URL was indeed correct? Also, please look at the requests when redirecting back to see if it's truly going to the api/oauth2 url. You should see something like 403 or 500 or something which would indicate your URL rewriting isn't properly configured or maybe your host is doing something weird when it's redirecting back.
Cheers.
I changed http.php last line to:
print Osticket::get_path_info();
And it stopped the redirect. In the URL I see on browser now there is microsoft error:
+is+not+configured+as+a+multi-tenant+application.+Usage+of+the+%2fcommon+endpoint+is+not+supported+for+such+applications+created+after+%2710%2f15%2f2018%27
So I guess there is an issue with the configuration (on the Microsoft side) and it breaks the redirect and doesn't present the error.
B0ydie
Ah, I understand. I put my "tenant id" (from https://portal.azure.com/#view/Microsoft_AAD_IAM/TenantPropertiesBlade) instead of "common" in the URL for Authorization Endpoint and Token Endpoint. It does kick back to osTickey but with a
"invalid_client" error.
Please follow the documentation steps as listed. You would see that you need to go to App registrations, click the app, go to the Overview tab, and click Endpoints for the actual endpoints to use (v2 Authorization/Token endpoints).
Cheers.
And I am having an issue when I go to authentic the email address after it logs-in, the redirect is to the sign-in page of osTicket and it doesn't seem to complete the entry.
Hi,
I have the same issue but on Windows Server 2019 and IIS. URL Rewrite is installed and enabled.
I tested it with Single Tenant Endpoints and Multitenant Endpoints (with the correct URLs).
That is not how you setup email authorization. Please follow our documentation step-by-step but instead use Multi-Tenant setup:
Cheers.
