-
-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use OAuth client id with a https (secure) redirect url #494
Comments
Sorry for the delay. Does the error displays straight, or after a delay? Do you have time to click on the link? I tried recently and the Outlook flow worked as expected for me. I will give another shot in the nearest day and let you know. |
Oh wait I just noticed the redirect scheme with |
Those are shell commands to retrieve the access token or the refresh token. So |
Yes. I've dug into this explanation by reading the code that manages the oauth flow. In oauth/src/v2_0/authorization_code_grant.rs it's also actually hardcoded the http scheme. |
Good to know. I retryed this approach without success. Trace of this try:
|
Great, we are going forward now. I see in the logs that it uses keyring for the client secret. I don't know how you put your client secret with backend.auth.client-secret.cmd = "shell-command-that-retrieves-secret"
# or using raw, not safe and not recommended (yet useful for testing purpose)
backend.auth.client-secret.raw = "S€cяэT" |
With About Himalaya: I first tried to configure the account without reusing pizauth; the interactive UI asked for client secret and I think that I just sent a blank line or I pasted a old client secret of Thunderbird (which was paired with a different client id). --
Every attempts failed with the same trace of my last message. Also I add that the connection attempt blocks for a minute ( |
Looks like I miss some piece of information there. I thought the client secret was mandatory. The code expects a client secret as well. So either Thunderbird has a special authority that I'm not aware of, or the flow should accept not to have a client secret. I will investigate and let you. |
Is your client id Can you tell me a bit more how you configured your Thunderbird and pizauth? Is it for a personal account (like personal outlook account) or for a company? |
Yes, that is the client id of Thunderbird (the desktop version) that I'm using.
Yes, with Outlook the client id must be "authorized" by the organization. My organization has authorized Thunderbird.
Thunderbird is not running on my machine.
For work accounts (two, one is issued by my gov), so company. |
Apparently that is the case. I quote from pizauth readme:
Emphasis mine. |
Interesting. I can try to make the client secret optional and see if it works for you. I let you know. |
Hi,
I'm exploring the project to replicate my current email setup which use mu, mbsync, msmtp, and pizauth (OAuth token fetcher/daemon). I compiled himalaya from git with OAuth2 and keyring features enabled (the repository's head at the time of compilation was commit
92814d6
).The issue is that I can read mail from account using standard IMAP, but OAuth authentication fails for my Outlook work accounts. Since I am authenticating as Thunderbird (authorized with HTTPS redirects on localhost), attempting to fetch mail gives the following error:
Config snippet:
I also tried to bypass this by reusing the OAuth tokens from pizauth, with these config lines (but I think I may have misunderstood some of the config keys):
Some logs:
The text was updated successfully, but these errors were encountered: