Configure a new services?

[hammerfunctor]

Hi there. Thanks for your work on this fantastic project. How can I configure a new service as before? I may have to use the microsoft consumers endpoints instead of the common endpoints due to my organizational restrictions. And, when I tried the client_id extracted from thunderbird, the process failed since the finishing uri http://localhost:8080/finish doesn't match the configured redirect URI. Many thanks!

[pdobsan]

On Mon, May 13, 2024 at 03:38:36AM GMT, hammerfunctor wrote: How can I configure a new service as before? I may have to use the microsoft `consumers` endpoints instead of the `common` endpoints due to my organizational restrictions.

Would you mind to post of your old mailctl services.yaml config file. I don't really want to go back on this but seeing your config might help me to find a solution for users in your situation.

And, when I tried the `client_id` extracted from [thunderbird](https://hg.mozilla.org/comm-central/file/tip/mailnews/base/src/OAuth2Providers.sys.mjs), the process failed since the finishing uri `http://localhost:8080/finish` doesn't match the configured redirect

That is an unfortunate things, I don't really understand why the redirect_uri should be registered in advance. Must be a Microsoft thing, other providers do not requite this, as it doesn't really make sense in my view. There were some unrelated reasons I've chosen /finish instead of root. Issue #44 reports similar problem.

[hammerfunctor]

Okay I fight with those microsoft thing and figured it out. For organizational account, the configured Azure app has to be a multitenant one, or things are just messed up. With a single tenant app, one either fails to login his email account (with consumers endpoint), or the app refuse to serve (with common endpoints). After setting up a multitenant app, things shall work if a localhost:8080/finish redirectURI is added.

Would you mind to post of your old mailctl services.yaml config file.

My old service file is almost the same as others.

Thanks!

[pdobsan]

On Mon, May 13, 2024 at 10:02:06PM GMT, hammerfunctor wrote: Okay I fight with those microsoft thing and figured it out. For organizational account, the configured Azure app has to be a multitenant one ...

Great. I wait for the others if that solves their problems too. If so I should put your trick into the docs. I don't have microsoft account so can't really experiment. Do you think getting rid of "/finish" would help? I have already tried to make redirect_uri configurable again but ran into unrelated problems.

[benasocj]

For organizational account, the configured Azure app has to be a multitenant one

Unfortunately, this workaround doesn't work for me, since I don't have admin access to the organizational account (as it is the case with others as well). Therefore, I would appreciate the problem being fixed through the software.

[pdobsan]

Release 0.10.1 set the redirect_uri back to http://localhost:8080. I hope this solves the problem for most of the microsoft account users.

If you already used @hammerfunctor 's trick then you need to do it again one more time.

[hammerfunctor]

Unfortunately, this workaround doesn't work for me, since I don't have admin access to the organizational account (as it is the case with others as well). Therefore, I would appreciate the problem being fixed through the software.

I don't have admin access either. You could try it.

[benasocj]

I don't have admin access either. You could try it.

Sorry, I should have been more precise: My organization isn't giving me access to the relevant sections in MS Azure and MS Entra in order to set this up.