Hi
I am trying to configure an Oauth connection to Microsoft. The documentation to do this is very comprehensive and seems to work fine up to a point. I configured the MS Azure side without issue, as per the doc.
The Redirect URI used was the one generated within SuiteCRM, which in my case was http://localhost/suitecrm8/index.php?entryPoint=setExternalOAuthToken
which is very similar to the valid example given in the documentation.
So, with the OAuth Provider side configured in SuiteCRM as well, without issue, I then started to set up the OAuth Connector using the next set of documentation to set up an incoming mail with OAuth.
The first step of this is to effectively authenticate SuiteCRM with Microsoft. I entered the values as explained and then pressed the Authenticate button, which does the initial Microsoft display, requesting a confirmation to grant permissions, so it is trying to connect to the right place. Then, upon acceptance we get a message that the URL was not found. This makes sense as in Windows, the file (Index.PHP in this case) needs to reside in the designated redirect location, and in our install, there is no Index.php in /suitecrm8.
When I changed the Redirect URI to add in the /public/ (where I start the main system from) or the /public/legacy/ it doesn’t error, just shows a blank screen and does nothing.
Clearly, there are a lot of ‘index.php’ files within the directory structure, what should I be telling Microsoft to point at ? all help gratefully received.
Hi @ggraynoth,
Thank you for the feedback.
If this is Suite8, and you have the vhost pointing to /<path-to-suite-8>/public, the url should be:
http://<path-to-suite-8>/legacy/index.php?entryPoint=setExternalOAuthToken
In your case:
Could you raise an issue on the SuiteCRM 8 repo with this problem, please?
I.e., that the generated Redirect URI is not correct in suite 8
SuiteCRM 8 repo:
Thank you
Thanks Clemente. I will try this now to ensure that it works and I will raise an issue on the SuiteCRM8 repo as per your link.
Many thanks in advance and I hope that this all works 
Regards
Gary
OK, so I tried it with the path that you indicated (I added an i in front on the ‘ndex’, which I assume was just a typing error), adding in the /legacy but this came up with a URL not found problem. See screenshot.
The legacy directory is a sub directory of public, so I then added in /public/legacy so that it was directed to the legacy directory containing the index.php file.
This got me back to the blank screen issue that I was having - see screen below.
There are a couple of things I can think of --if the /public/legacy is correct and should work, I was wondering whether the Secret value in the OAuth providers screen may be incorrect. It says in the documentation that you need to keep the secret Value field to use in SuiteCRM8. There is also a Secret ID field. I have used the secret value in the SuiteCRM 8 field in OAuth Providers in admin. Is this correct ? if so, I am at a loss as to what I may have done wrong.
I am tempted to go into Azure and remove the App and do it again from the start with a new ID and see if that sorts it out. We are clearly getting through to the MS site as when I made a typo in the Redirect URL and they didn’t match, I got a full MS error page with MS logo etc… so it is just getting over this blank screen issue, so that I can get the other authentication fields populated.
Any other suggestions ?
Many thanks for your help so far.
Clemente, just to let you know, I have raised an issue on the Github page, as requested.
Gary
Hello!
Were you able to solve this problem? I’m with the same thing!
Hi Fernando.
Apologies for the late reply but no, We never got this resolved.
It is either an entry point issue or there is some security code somewhere which is stopping access, but this will be hard to find.
I also tried google calendar integration, following the SuiteCRM documentation and got exactly the same blank screen problem on the final step of linking this into the SuiteCRM user.
I gave up and we continue to use outlook outside of SuiteCRM and just use the calendar and calls inside Suite from the modules.
Not really the solution we wanted but didn’t really have more time to spend solving this.
Sorry.
