Cannot Authorize Yahoo Account in Bichon using OAuth2

Open
  • Is something wrong?
#193 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
authentication, backend

Research direction

Start by comparing Bichon’s Yahoo OAuth authorization and redirect URL handling with Yahoo’s linked OAuth2 authorization code flow documentation. Reproduce the reported “invalid redirect URL” response and trace how the redirect URL is constructed and sent; completion means Yahoo authorization succeeds with a configured redirect URL. The issue does not name relevant source files or tests.

Written by the indexing model from the issue text.

Description

question
Description

I am trying to add Yahoo via OAUTH2 (I try not to use app passwords if I can help it)
I am following Yahoo's Developer Documentation for OAuth2 here
i.e. Using the authorization, token URLs outlined in the document, etc.

However, I am unable to complete the authorization workflow

Notably, whenever I try to authorize using Bichon, I get "invalid redirect URL" on the Yahoo side, no matter the variant I try to add to my application's redirect URL list under Yahoo's developer settings

I can provide more details later (my rapid diagnostics resulted in constant 429s from Yahoo for a bit...)
Hoping we can figure out how to get Yahoo's OAuth working with Bichon as well
Maybe there's something in the linked docs that sticks out/might require different handling on our side, I have no idea.

Related Issues

This was technically previously reported in #183, but the user came to an alternative solution, and this was never really "solved"
Didn't want to add onto a closed issue, either
That being said, at a glance, it seems like using OAUTH2 might be possible for Yahoo accounts

Dominant language
Rust
Stars
2.1k
Forks
91
Avg merge
14h 54m
Merged PRs (30d)
6

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rustmailer/bichon

All issues in rustmailer/bichon

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.