14. Oktober 2022 um 13:54 Uhr - Views: 648 #14028AnsweredDragan DobricTeilnehmer
We are trying to create mail account using OAuth with IMAP as described in Docs » Communication & Notifications » PostMaster Mail Accounts.
Everything goes fine until saving the new created account.
There, when we click on the save button, we are supposed to login on the office365 account (which we did) and redirected to OTOBO customer’s login page.
So when we go back to admin panel » Mail Account Management newly created account doesn’t exists. It is not possible to fetch mail.
Our version of OTOBO is 10.1.5 – Docker based installation.
Also we first tried with the older version 10.0.11 who was migrated from OTRS, and then with 10.0.16 but with same results.
Any help would be apricate?
17. Oktober 2022 um 11:17 Uhr #14045marcel-grafTeilnehmer
use you the otobo server with http or https? With http, you must change the Redirected URL from https to http.
18. Oktober 2022 um 9:51 Uhr #14059B OTeilnehmer
did the above mentioned solution from Marcel solved your problem, cause I’m facing exactly the same issue.
27. Oktober 2022 um 9:42 Uhr #14152
In fact, the Otobo server already uses https.
However, my certificate has expired, which should be the reason of this problem.
Marcel’s advice definitely directed me in this direction, and (hopefully) after I’ve solved it, I’ll report back here.
2. November 2022 um 9:05 Uhr #14184Michael EißlerTeilnehmer
did you find a solution for your issue? I´m facing the same.
No Mailaccount after the redirection to OTOBO login.
2. November 2022 um 15:55 Uhr #14192
No, still no solution for this…
So problem is that https://<My OTOBO address>/otobo/index.pl?Action=AdminMailAccount not respodning…
We tried everythin from the documentation
also, everything in Azure look good.
Are there any tips? Could I test this endpoint somehow?
- Diese Antwort wurde geändert vor 10 Monaten, 4 Wochen von Dragan Dobric.
2. November 2022 um 17:04 Uhr #14194Best AnswerStefan RotherVerwalter
you need to change
in your OTOBO FQDN. What is your OTOBO FQDN and what did you add to azure as redirect url?
When an error like this occurs, something is wrong with the configuration.
Either something is not set up correctly in Azure, or something is wrong in OTOBO.
I’m not really familiar with Azure either, but I’ve already been able to help about 10-15 of our support customers by going through everything again and check all values.
2. November 2022 um 23:55 Uhr #14195Michael EißlerTeilnehmer
I found the solution for me. I enabled „SessionUseCookie“ in System Configuration –> Core –> Session –> SessionUseCookie
My assumption is, the login in Otobo after the redirection from Azure is interfering the authentication process.
Note: I also enabled SessionUseCookieAfterBrowserClose, but I think the above mentioned setting was the important one.
Hope this helps you also!
9. November 2022 um 8:48 Uhr #14224
Stefan’s proposal was correct 👍. There was wrong letter in the redirect url.
As I myself have no access to the company’s Azure tenant, I created redirect url manually and compared with the one that’s generated from the Azure, so that’s how I founded it actually…
Also, after I fixed it I played around with the Michael’s tips regarding setting „SessionUseCookieAfterBrowserClose“ but it seems like there is no impact on this.
- Du musst angemeldet sein, um auf dieses Thema antworten zu können.