OAuth2 not redirecting | IIS 10 PHP 8.x
You still need to check what I mentioned above.
Also, are you using v1.17.2 and the latest versions of the plugins?
Lastly, as long as the attributes are correct in your OAuth2 config it should allow the username and email address.
Cheers.
KevinTheJedi
tested it but it is not case sensitive!
I tried a new installation of osTicket with a new DB and eMail-Konfiguration works fine. I have taken the same settings on both osTickets-Installation.
After I updated the tables in the Database excepting config, plugins, etc... the redirection doesn't work anymore.
So this must be due to an wrong entry in one table!
Tables which I have not migrated:
ost_syslog
ost_session
ost_schedule_entry
ost_schedule
ost_role
ost_plugin_instance
ost_plugin
ost_lock
ost_list_items
ost_list
ost_group
ost_filter_rule
ost_filter_action
ost_filter
ost_email_template_group
ost_email_template
ost_email_account
ost_email
ost_draft
ost_department
ost_content
ost_config
ost_canned_response
ost_api_key
- Edited
KevinTheJedi
Because there was either no change or for test purposes such as ost_config
The point is: In which table could be an Entry belonging to oauth2 authentication and redirecting.
A new installation of osTicket with a fresh database is working on oauth2 and email-redirecting.
When I copy the data of the old tables of the database to the new one - keeping the entries of new-installation - it doesn't!
So there must be an entry in one of these tables which impede the functionality.
I thought the entries for email-settings are only in
ost_config,
ost_email,
ost_email_account,
ost_plugin,
ost_plugin_instance,
but there must be more which I have not figured out yet.
Those are the only tables for email auth related settings, yes. If you are migrating data then migrate the entire database and reconfigure each email.
Cheers.
KevinTheJedi
I testet this also - but the result is the same
very annoying
is there a possibility in osTicket to change the name of the database easily
Hi,
I just wanted you to know that I find out what caused the failur in our osTicket.
The problem was made by the Redirect-URI due to it seems to be case-sensitive at MS site.
So on osTicket I copied the path from the explorer with upper case letters and at MS365 Azure I put it in manually only with lower case letters.
So simple but very effective...
Thanks for posting this..