timo - Profile

When I do this I get this => "Page Not Found, The page you are looking for could not be found. Check the address bar to ensure your URL is spelled correctly. If all else fails, you can visit our home page at the link below." I havemade a OAUTH CLIENT as according to the manual. Should there be a connection in de xml file with this token?

View Comment

v4 doesn't work with SAML authentication

Support October 7th, 2020 @ 12:40 pm

I don't see the possibility to log in with the right one because the Outlook app crashes before I can do anything.
See https://store.suitecrm.com/support/SuiteCRM-official-outlook-plugin/3065

View Comment

Not possible to load an add-on in Outlook.com

Support October 6th, 2020 @ 8:13 am

Any news?

View Comment

v4 doesn't work with SAML authentication

Support October 6th, 2020 @ 8:13 am

Thank you for the information and I will check if this is a solution for #3065

View Comment

Not possible to load an add-on in Outlook.com

Support September 21st, 2020 @ 7:40 am

Hi, yes it is possible to do that. Only after that I get problems. I can load this add-on. Only after the installation I went to the configuration menu for this add-on. It looks like there is a loading problem again. I cannot do anything. See the screenshot below. Is this custom Outlook Manifest File Not supported or might there be a single sign on problem?

In the configuration menu for this add-on

In the web console (network) of MS Edge I see now something interesting.

I get the message status (failed) net::ERR_TOO_MANY_REDIRECTS (document) ==> SA_Outlook/?et=
often this SA_Outlook/?et= in combination with status 301.

Header general

Request URL: https://our.crm.url.test/public/plugins/SA_Outlook?et=
Referrer Policy: origin

Response header

content-length: 265
content-type: text/html; charset=iso-8859-1
date: Fri, 11 Sep 2020 06:40:09 GMT
location: https://our.crm.url.test/public/plugins/SA_Outlook/?et=
referrer-policy: strict-origin-when-cross-origin
server: Apache
status: 301
vary: User-Agent
x-content-type-options: nosniff
x-robots-tag: none
x-xss-protection: 1; mode=block

Request header

Provisional headers are shown
Referer: https://outlook.live.com/
Upgrade-Insecure-Requests: 1
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.102 Safari/537.36 Edg/85.0.564.51

Header

fetch("https://our.crm.url.test/public/plugins/SA_Outlook?et=", {
"headers": {
"upgrade-insecure-requests": "1"
},
"referrer": "https://outlook.live.com/",
"referrerPolicy": "origin",
"body": null,
"method": "GET",
"mode": "cors",
"credentials": "omit"
});

Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 404 (Not Found)

Although we do not use the same tech, our problem might be the same as the one below. "v4 doesn't work with SAML authentication"We're using Azure AD for single sign-on, and apparently v4 doesn't work when SuiteCRM is using SAML for authentication, claiming that the password is invalid.

Source
https://store.suitecrm.com/support/SuiteCRM-official-outlook-plugin/3047

View Comment

v4 doesn't work with SAML authentication

Support September 11th, 2020 @ 12:32 pm

Hi, it looks like we have the same problem only we don't use Azure. Can you tell more about this work-around?

View Comment