KevinTheJedi

it worked for now with fresh installation of App and Plugin .

now when configuring Remote Mailbox
cannot connect to host ; error = fsockopen(): Unable to connect to outlook.office365.com:143 (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond) (errno = 0 )

KevinTheJedi
DvDaf

Can confirm that this has not fixed my issue. I have been working with MS support as well, but they have not been able to see any issues with my app registration or other parts of the setup.

DvDaf

DvDaf

Thank you so much. It worked for me.

For future reference, I set up osTicket with IIS and Window Server 2019. I was struggling with this error because I wasn't too familiar with language in the php.ini file. As the solution, I removed the semicolon in the front of curl.cainfo to uncommented it.

Kind regards,

lstrom

Your initial issue was that URL Rewriting is not enabled on your webserver or if it is it's not running correctly. Did you ever solve that issue?

Cheers.

KevinTheJedi

Sorry, I do not mean to be obtuse. This is fairly new territory for me. I have looked at a number of other posts in these forums and I am seeing the rewrite rules that others have shown:

Testing the "HTTP api" rule, I get the following result:

So that seems to be in-line with the result of being sent to the main /portal page

I'm guessing I may need to edit the rule to point to the agent panel or admin panel, is that thought in the right direction?

lstrom

No, we ship with web.config that your IIS should be loading but appears is not. You need to figure out why that file isn’t being loaded.

@ntozier Do you know how to force IIS to load the web.config properly?

Cheers.

KevinTheJedi

Okay, so the appearance of the rules does not indicate that the web.config file is loading. Good to know, thank you.

Does this have a solution? No matter what I try, I end up with:

Sorry, but we’re having trouble signing you in.
AADSTS9002325: Proof Key for Code Exchange is required for cross-origin authorization code redemption.

mangoo

I’ve never seen that one before. Follow our documentation to a "T". If you still have issues after that then contact MS for further assistance.

Cheers.

mangoo

Then you didn’t configure something right in your Email Config. Please post a screenshot and censor any sensitive info.

Cheers.

Here it is:

KevinTheJedi

Did you mean that screenshot?

KevinTheJedi

For the Client ID did you use the Application (client) id from Azure?

Yes.

Also, for the Client Secret did you use the Secret Value or ID from Azure?

Yes.

You should be using the Secret Value from Azure.

Both answers - yes.

mangoo

No you are pointing to the Secret ID which is not correct. You need to use the Secret Value.

Cheers.

mangoo

It is VALUE! Not Secret ID. Sorry, I was blind. Seems working now!

mailbox: OAuth2 Authorization Successful

mangoo Also, had to do this to enable SMTP:

https://learn.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/authenticated-client-smtp-submission

Use the Microsoft 365 admin center to enable or disable SMTP AUTH on specific mailboxes

Open the Microsoft 365 admin center and go to Users > Active users.

Select the user, and in the flyout that appears, click Mail.

In the Email apps section, click Manage email apps.

Verify the Authenticated SMTP setting: unchecked = disabled, checked = enabled.

When you're finished, click Save changes.

Otherwise, was getting:

5.7.139 Authentication unsuccessful, SmtpClientAuthentication is disabled for the Tenant. Visit https://aka.ms/smtp_auth_disabled for more information. [AM5PR0502CA0017.eurprd05.prod.outlook.com]

KevinTheJedi
@ntozier

Just following up on this after the weekend. I am no IIS guru, but I did stumble upon the "configuration search" tool in the Configuration Editor and gathered the screenshot below. This appears to show that it is using the web.config shipped with OsTicket, but my attempts to learn how to verify this have not yielded anything to this point.

lstrom

Then it should be working. Look at the API rule in your screenshot.

Cheers.