OSTicket + O365 + Oauth2 = foobar: Page 2

OSTicket + O365 + Oauth2 = foobar

KevinTheJedi

That means you do not have URL Rewriting enabled properly or most likely the web.config we ship with the software isn’t being loaded properly. You’ll need to figure out why the web.config isn’t being loaded properly. Someone else in the community shared how they got it working. You can search for this thread in the Forum.

Cheers.

GFY

Outgoing is just SMTP/no auth to a relay.
Email Settings:

GFY

Tested the cron from the cli, no errors...looking at the cron log, it does look like it is executing.

KevinTheJedi

GFY

Do you have any Ticket Denied errors being logged in the system logs? At this point I’m at a loss. If IMAP is enabled and you have email fetching enabled and you have a valid cron job that is executing successfully then it should be fetching tickets.

Did you configure a specific folder to fetch from?

Cheers.

GFY

I don't. It is weird, the cron is obviously executing, but no OST System logs are being generated. It is pretty clear that the mailbox is not being accessed...and the only error I've been able to dig up is that cred error in the DB.
I configured the INBOX folder for the fetch.

GFY

Kevin, is there somewhere the OAuth2 plugin stores config info other than the DB? I would like to wipe out any config info to make sure it is holding on to any bad data. I am going to clear all the email configs and plugin and start over. Going to delete the App Registration as well.

KevinTheJedi

GFY

Did you set your cron job to use PHP 8?

Did you explicitly set INBOX or left that field blank? If you typed INBOX then clear that and retest. We default to INBOX so you don’t need to put that there.

Config only in config table.

Cheers.

GFY

I did not set cron to use PHP8, but PHP 8 is the only PHP version installed? Is there something that needs to be changed?

I cleared all the settings, deleted the app registration, uninstalled the plugin, reinstalled the plugin that comes with the 1.17 download (has an earlier mod date). I reset everything back up making sure not to specify "INBOX" as it is default. The setup and authorization went smoothly...it is still down though. I am searching through all the system logs now and looking in our tenant for any errors.

KevinTheJedi

GFY

Yea then I don't know why it's not fetching. We covered every relevant setting and you seem to have everything configured correctly. I have O365 fetching and working so I'm completely unsure what's happening in your case.

Cheers.

GFY

This happens every time I configure the main mailbox account. I have to re-enter these fields and re-enable the email fetching. I then re-auth the config through the tenant and after a little while they just disappear.

GFY

Yeah, the settings do not stay. After I set everything up, if I just refresh the settings revert. back to what is shown above.

KevinTheJedi

GFY

Then you have a deeper issue apparently. Those settings should be saved once you click Save Changes at the bottom of the page.

Cheers.

GFY

Things were working great until 1.17. I have reset the permissions on the database for the osticket user, but still nothing save and no database errors to see.

GFY

Kevin,

The entries still can't be saved. No database/php errors are logged. I changed the values using phpmyadmin to what they should be. I then did B0ydie's solution for the app authorization because the way you are supposed to authorize apps wasn't working:

https://forum.osticket.com/d/101542-oauth2-plugin-error/9

so evidently what worked was basically removing restrictions on azure then putting them back once its logged in. it is s security risk to a point. this is what MS sent me to fix it

Log in to the Azure Active Directory admin center.

Go to Enterprise applications > Consent and permissions > User consent settings.

Under User consent for applications, select Allow user consent for apps

then i put it back to normal after its logged in, once it has its keys it seemed to work

Now, at least the emails can be retrieved. We are still testing, but I am thinking v1.17 needs some work.

adestrella1027

Not to hijack the thread here but am I reading the localhost method must be configured from the osTicket server itself (in a web browser)? That's what seems to be happening as I'm configuring it from my remote pc and it's redirecting to localhost.

KevinTheJedi

adestrella1027

Yea either you need HTTPS or localhost. If using localhost it must be done from a browser on the server. If you have issues with that please raise a complaint with MS as they impose these restrictions.

Cheers.

« Previous Page