Hi,

I have managed to get this to work fine when users can consent, however, when the admin consent request is enabled i keep getting the following after it's been approved and redirected. (Rewrite is correct on Apache2 and working)

This is returned from Azure.
=AADSTS65004%3a+User+declined+to+consent+to+access+the+app.

Ive tried the fixes mentioned above:

• grant admin consent twice, once on the API Permissions and again under Enterprise Applications > click app > click Permissions > grant admin consent.

However, the same occurs.

I've just tried this on a separate tenancy's with the same admin flow to replicate the issues and I see the same.

Has anyone else seen this or have any insight to get this to work?

I can of course give that user admin rights and it succeeds but I cannot do this in a production environment.

Thanks.

SC

megatronic79

User+declined+to+consent+to+access+the+app. as the error states a User denied the consent to the app. You will need to consent in order to get a Token.

Cheers.

KevinTheJedi

Thats the prob thou, user cannot do that, it's sent to the admin for approval.

When the approval is done BY the admin the user clicks on the return and redirects back to osticekts, however it seems you are dropping the client-side approval... hence the returned message from azure. The user cannot do any more than that, and all settings are applied on the azure side.

I've tested this on two separate tenancies. if I turn of the approval flow it works as expected, when it's on this part breaks it doesn't appear you can complete the auth.

In this specific backend scenario - are you able to test on ur instance?

megatronic79

Yea that won't work, you'll need to allow them access to grant consent. We have some updates coming soon that shouldn't force prompt=consent which might help in your case. In the meantime you can download the plugin raw files from github, hydrate them, and make the change yourself to not force the prompt or you can wait for the next set of updates to be released.

Cheers.

KevinTheJedi

thanks mate! will give that a crack. appreciate the quick response.

@KevinTheJedi having a similar issue. After O365 auth is complete, i click 'save' and it gives this message. I've triple checked to verify imap/pop still enabled on the account and followed your guide for the O365 Aure AD application. A little stuck

travisn

Then you’ll need to contact MS for further assistance.

Cheers.

KevinTheJedi Changing to pop and 993 gives an error saying : last request failed

travisn

Because port 993 is IMAP, not POP.

Cheers.

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.

KevinTheJedi

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

Thanks for your help, mate.

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.