Creating a Ticket via Email

KevinTheJedi

The error states that SSL is disabled in your install of PHP. It seems you just need to install/enabled the php-openssl extension. If all else fails you should reach out to your server admin and/or hosting provider for further assistance.

Cheers.

Muneer-Jahangeer

KevinTheJedi

Fab!

After enabling the OpenSSL extension, I was able to configure the remote mailbox successfully, but when I enabled the email fetching option, I encountered an error,

KevinTheJedi

Muneer-Jahangeer

Then I suspect the account you used doesn’t have the appropriate permissions to authenticate on behalf of the shared mailbox. Did you add the account you authorized to the Send as and Read and Manage permissions for the shared mailbox?

Cheers.

ramrajone

Muneer-Jahangeer
If, all account info is correct and permission is. It could be a cache issue you could try another browser or another option would be to delete the email and re-add it.

Muneer-Jahangeer

KevinTheJedi

I added my logged-in account to all three mailbox permissions and enabled it again, but the same issue persists.

My default email is not shared. just a active o365 user.

KevinTheJedi

Muneer-Jahangeer

Do you have the IMAP permission allowed for the shared mailbox?

Cheers.

Muneer-Jahangeer

KevinTheJedi

Note: My default email is not shared. just a active o365 user.
Yes, IMAP and other options are already enabled,

KevinTheJedi

Muneer-Jahangeer

Did you sign in to the email you configured in osTicket when redirected to Microsoft? Does the Resource Owner in the Token tab of the OAuth2 Config popup match the email in osTicket?

Did you enable the two checkboxes for Access Tokens and ID tokens in the App Registration?

Cheers.

Muneer-Jahangeer

KevinTheJedi

Sorry for the delayed response as my shift just started.

No, sorry, I'm using a different admin Azure sign-in to log into OSticket. When accessing the OAuth2-Microsoft configuration, it doesn't prompt for login; instead, it directly leads to the OAuth2 authorization page. Do we need to configure the remote mailbox using the correct resource owner? Also, I noticed that the token expired yesterday but wasn't auto-refreshed

Also i just enabled Access tokens and ID tokens in Azure App registration section.

KevinTheJedi

Muneer-Jahangeer

Then try to re-authorize and make sure you have a running cron that works.

Cheers.

Muneer-Jahangeer

KevinTheJedi

When I clicked submit, the token renewed only for one hour. so I have adjusted the task scheduler to run every hour and repeat daily. I will provide feedback after one hour to confirm whether the cron task scheduler is running successfully

but remote mailbox is still failing,

KevinTheJedi

Muneer-Jahangeer

Then you need to check the authentication logs on the Microsoft side to see why it’s failing.

I will say that if the resource owner does not match the email you are configuring in osTicket then you should add the resource owner to the "Send As" and "Read And Manage" permissions of the email you are configuring in osTicket (within the exchange admin center or normal admin center).

Cheers.