Have you selected the correct folders here, or is this where the problem arises? (this one happens be be a gmail connection, but just for example)
Hi again
This is when I try to select the folder by clicking on the “Select” button… The error is raised then.
What do I miss then ?
Thanks Stevens
Xavier
EDIT : this is not a gmail OAuth here, but an Outlook365, if this matters…
Hi everybody,
Is anybody have an idea of why all is working except the folder listing when configuring the inbound account ?
For the record, I have also checked the php (8.1) module : imap and zip are correctly loaded.
Right now, I have “connection successfull” for the Oauth on the inbound account, but when I try to click on select for the folders, nothing is shown…
If somebody could give me a way to find what is wrong, this could save me…
Thanks in advance,
Xavier
I don’t know if this will help or not.
Try to quick repair and build from admin account.
Click admin → Repair (Under system section) ->Quick Repair and Rebuild.
Also, clear cache from browser and login again.
Also, you have “Repair Inbound Email Accounts” option under repair.
Hi Shub,
You dont know how many time I have “repaired”, cleared cache, etc…
Not working after days of trying at 2 persons and didnt find much help except from PStevens, the forum in every possible language found, the doc. That was not enough to allow to find “why” and “how”.
In my opinion, SuiteCRM is a really great tool but without big enough community. Except some “pros” who dont really have time to “help all the little people”, I did not found a support for SuiteCRM (but I’m maybe wrong and I did not look correctly or ask to the good people !).
Is there existing pro support ? Does people propose this ?
Best,
Xavier
Sure
Read, read, read again, and again, start over maybe 10 times, start over on Microsoft azure too, no success at the very last step : the inbound account imap folder read. All is working except that the folders are not raised at all (as many other encountered on many other threads).
All solutions suggested tried, but nothing works at the end.
All this is only true with Oauth on Microsoft since they activated Oauth and no legacy mode.
Best,
Xavier
@pstevens is your man for inbound email issues. Pay him for a couple of hours of consulting and put him in a remote session looking at your server.
I do have detailed setup instructions, but they are written specific to one of my clients that I helped setup, so I can’t really share them publicly. The client did most of the work on the Azure side and I did the setup on SuiteCRM side. It wasn’t easy, and there was a lot of back and forth, but we did end up with a repeatable process. I only have really detailed instructions the SuiteCRM side though, but I’ve done it a few times.
The SuiteCRM documentation didn’t exactly work for us. Particularly in setting up personal accounts. What we had to do was setup like an admin account on the Azure side that was able to connect and get a Oauth grant for a group account, then everyone just used that grant to verify their personal accounts. It worked, one draw back is that anyone could essentially add anyone else’s account in the company (It’s so complicated to setup good luck to the users though trying to access someone else’s account LOL!).
OH and one main point I can share DON’T TEST THE CONNECTION!!! that kills it. If you can select folders, you are connected. If you don’t see folders and cannot select them, you are not connected. Dont’ press the “test connection settings” button.
Is there an issue on GitHub for this?
If it is so reproducible it shouldn’t be too hard to fix…
Next time I have the occasion to do it, I’ll confirm if that’s still an issue. It’s been a couple of months since I did it and I just have in big bold letters in my notes not to test the connection. I seem to remember if you press that, it doesn’t connect and times out. However, if you just select the folders and then save, it all works and you’re good.
I’m back after some time leaving this problem with a good news : today, I went back to the CRM and strong of the last comment from PGR (Pstevens wrote “Main point, DONT TEST THE CONNECTION”), I have tried again… and get this working !!!
I want to apologize for my last messages, I was disappointed, discourraged and lost alone with a problem wihout exit and was very sad.
I know we are on a forum and every one have a life, dont have to be here for all the “small users”, but without all this small message and tips given here, I wouldnt be able to succeed.
So, thanks to all of you for your time, your patience and your understanding
With many others posts found on the forum and the net, I have been able also to understand some strange behavior (the SSL/TLS dropdown still showing “no” after saving but saving effectively in the database for example).
Thanks again to all of you, especially Pstevens and Pgr
Xavier
Thanks @Chabi02 glad it worked for you. Maybe you could return the favor (to me and the community) by letting us know if the SuiteCRM documentation about the Azure side of things works as is, or you had to do anything different. That would be super helpful, as I don’t have Azure personally so I only have the experience on the SuiteCRM side of things.
Hi
I prepare a full doc and post it when ready !
Thanks again for all
Xavier
It looks like there was a PR released with 7.14.1 that supposedly fixes this “test connection” hangs and fails. Also, this commit also supposed to help test connection. Are these fixes also in 8.4?
Hi everybody,
So to help anyone else who need this, here is all what I did to get Oauth2 working on SuiteCRM8.
First, here is all what I have done on Azure to get this working on my side.
My screenshot are in french, but you will be able to find out the most important part in english views.
On Image1 : you have all the things done : name of the app, id of the app, id of the object, id in the directory, certificates, Redirect URL, URI id of the app. That’s a summary.
On Image2 : you have all the end points listed.
On Image3 : I have the certificate with the secret ID.
On Image4 : I have set the redirect URL
On Image5 : you can see how I have set the rules for feeds
On image7 : this is a very important part, the scopes used. Check here the 4th column (with “Non” for “no” and “Oui” for “Yes”), this is the column for “admin consent”.
With all this set, I have follow the doc and set only a group address (to allow me to have the automatic import for emails).
All this have been working with in this order :
- Set the External OAuth Connector - Type : personnal
Name : Microsoft
Perimeter, 4 lines (in this exact order) :
- offline_access
- https://outlook.office365.com/IMAP.AccessAsUser.All
- User.Read
- User.Read.All
set here also the id of the app, the authorize token (from Azure), the url to the token (from Azure)
Set also additionnal config :
-
Get Token request grant type : authorization_code
-
Refresh token request grant type : refresh_token
-
Set the External OAuth Connection :
Type : personnal
name : full email
Token : Bearer
Choose the External Oauth Connector
→ Identify to retrieve the 2 keys to allow connection.
Carefull here : I had to identify one time as admin (check the beginning of this list for Azure)
- Set incoming emails with OAuth
Type : group
Smtp server : outlook.office365.com
SSL - Port 993
Set also the Oauth connector.
When all is set, then DONT TEST THE CONNNEXION, just broswe the folder and they raise.
Then save and you are ok.
The outgoing email account is easier to set up (smtp.office365.com), classic set up.
Tell me if this is ok with all these elements
Hi pstevens,
Not to open another can of worms, but would you be able to help with connecting OAuth with gmail too?
I’ve tried all the instructions and documentation, but when clicking the test connection button (before i read this post) i just get a blank white screen.
Self hosted
SuiteCRM 8.5.1
Never click the test connection button. If you click on folders and get folders, you are connected. In my experience the button does not work.
Hi
The tip for “not click the test connection button” have saved my life and my time before !
Best,
Xavier