OAuth2 Microsoft Not Working: Page 7

OAuth2 Microsoft Not Working

KevinTheJedi

Because port 993 is IMAP, not POP.

Cheers.

travisn

KevinTheJedi Whoops. Its Monday. Changing it to IMAP (still 993) gives "AUTHENTICATE failed." And this is after getting through the O365 auth process.

KevinTheJedi

travisn

Then either you didn’t configure the App in Azure correctly which you can follow our documentation to ensure you did everything correctly or you need to contact MS for further assistance.

Cheers.

lstrom

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.

megatronic79

KevinTheJedi

I changed consent to login and rehydrated, I can confirm it works as expected in this stricter setup.

Thanks for your help, mate.

atahaynah

KevinTheJedi

this is the error that i am receiving
/Osticket/scp/ajax.php/email/4/auth/config/mailbox/oauth2:msmail:1 Failed to load resource: the server responded with a status of 500 ()

Request URL: https://"localserver"/osTicket/scp/ajax.php/email/4/auth/config/mailbox/oauth2:msmail
Request Method: POST
Status Code: 500
Remote Address: **********:443
Referrer Policy: strict-origin-when-cross-origin

atahaynah

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

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.

toann

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

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?

KevinTheJedi

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.

lstrom

KevinTheJedi

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

lstrom

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.

mangoo

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.

KevinTheJedi

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

KevinTheJedi Looks like I had the URLs messed - didn't know that URL and was "randomly" trying whatever I found in the forum.
However, this still doesn't work for me - after accepting Microsoft-side popup, Osticket shows: "invalid_client".

KevinTheJedi

mangoo

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

Cheers.

mangoo

Here it is:

KevinTheJedi

Did you mean that screenshot?

KevinTheJedi

mangoo

For the Client ID did you use the Application (client) id from Azure? Also, for the Client Secret did you use the Secret Value or Secret ID from Azure? You should be using the Secret Value from Azure.

Cheers.

mangoo

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.

KevinTheJedi

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

« Previous Page Next Page »