Hello... I followed all the instructions, and allow in the authorization window the account and permissions do not error for the Microsoft side. But in OST appears an "invalid client" error. I double checked the info, and even put a wrong client id for testing (and Microsoft windows show error " Application with identifier 'xxxxx-xxx-xxx-xxxx' was not found in the directory" so I'm sure the "client Identifier" is well...

osTicket (v1.17-rc4) on centos 8

    lupo_gris

    Please post a screenshot of the OAuth2 information you are using. Please make sure to censor things like the client secret, client id, tenant id, etc.

    Cheers.

        lupo_gris

        I guess you didn't read the post I linked above with full instructions. Your Resource Details Endpoint is incorrect. You should be using the v2.0 outlook api url https://outlook.office.com/api/v2.0/me. Please make sure you download and install the latest build of the OAuth2 plugin from our website.

        Also, your scopes are wrong. You need to use the outlook scopes of offline_access https://outlook.office.com/Mail.ReadWrite.

        Cheers.

            BrunoLopes Did you manage to solve it? I tried with incognito, but I still get that Email Mismatch.
            To get that error, I log into a shared mailbox after it asks me to sign with an admin account to authorize the access to the organisation.

              KevinTheJedi I made the changes, but still in "invalid client".. I download and reinstall the plugin with the same result

              edit:
              I made a fresh install, without de data of the old OST, and work... so something about the original OST is broken...

                  lupo_gris

                  Did you enable and consent to the needed scopes in your Azure App? Please go back to my linked guide and follow all the steps.

                  Cheers.

                      lupo_gris
                      These settings have worked for me

                      email Address Attribute part, you have different, based on your AD settings

                      Client Id: *
                      IdP Client / Application Identifier

                      Client Secret:
                      IdP Client Secret

                      Scopes: *
                      Comma or Space separated scopes depending on IdP requirements
                      offline_access https://outlook.office.com/IMAP.AccessAsUser.All https://outlook.office.com/POP.AccessAsUser.All https://outlook.office.com/SMTP.Send

                      Authorization Endpoint: *
                      Authorization URL
                      https://login.microsoftonline.com/common/oauth2/v2.0/authorize

                      Token Endpoint: *
                      Access Token URL
                      https://login.microsoftonline.com/common/oauth2/v2.0/token

                      Resource Details Endpoint: *
                      User Details URL
                      https://outlook.office.com/api/v2.0/me

                      Email Address Attribute: *
                      Please consult your provider docs for the correct attribute to use
                      emailAddress

                      Callback Endpoint: *
                      Redirect Uri
                      https://YourSupportTicketAddress.com/api/auth/oauth2

                        Our token expired and app won't fetch emails. So, app should have extra permissions in Azure App? Anyway, on SMTP configuration token is valid.

                        Update: After go to setting token and click on confirm, token refresh and valid but still main won't fetch emails form Inbox.

                          I tried with plugin version 0.3 and the redirect url does not work. it just redirects to the homepage when authenticating.
                          Version 0.5 does not open configuration, just a blank popup.
                          Any here with a working version?

                            sander4000
                            Check the network traffic with the developer tools (usually "F12"). Sometimes it shows you the error as soon as you got redirected.

                              KevinTheJedi yes, all configuration are correct... in a fresh ost (without data) works perfectly... I made a pre version upgrade (1.14 - 1.16) and from 1.16 to 1.17 and the OST with data works.. thanks a lot for the help

                                Is the scope of what is being worked on just generating the token? Is fetching and sending mail also implemented?

                                  leonlongoria

                                  Of course. We completely changed the package for mail from PEAR to Laminas-Mail which supports Modern Auth.

                                  Cheers.

                                    I must be missing something. I'm on 1.17rc4 and this is what I'm seeing:

                                      leonlongoria

                                      fyi for this issue, our organization was doing something weird with our firewall and SSL certs. After going around that everything worked. thanks

                                        MontanaMac

                                        You have cURL issues on your server. Please follow the link displayed in the error to review the possible resolutions. this is outside the scope of osTicket software.

                                        Cheers.

                                          margol

                                          I have no idea why; I am unable to replicate this..

                                          Are you using a test application? Are you sure you set the token expiration to a long period of time?

                                          Cheers.

                                              update: so the curl error was because of having "organizations" in the urls, changed them to "common" and now it appears to do nothing when saving the config, it just dumps me back to the login screen of the ticket system.