[bug] OAuth Returns "Invalid Username/Password" on Certain Apps #704

New Issue

Open

opened 2024-02-23 02:51:23 +00:00 by deadsuperhero · 3 comments

deadsuperhero commented

2024-02-23 02:51:23 +00:00

Your setup

OTP

Extra details

No response

Version

Latest Stable

PostgreSQL version

No response

What were you trying to do?

I'm trying to set up some integrations with the Masto API implementation. Most apps work, but I'm having a hard time with these two:

Buffer
Jetpack (from WordPress)

What did you expect to happen?

The approve button should complete the OAuth step and redirect, finishing the cycle.

What actually happened?

When I try to log in with certain integrations via the MastoAPI, I get stuck at an OAuth screen that doesn't actually let me log in.

Regardless of whether the credentials are correct or not, I get the message "Incorrect Username / Password" when trying to Approve the app.

Logs

No response

Severity

I cannot use the software

Have you searched for this issue?

I have double-checked and have not found this issue mentioned anywhere.

### Your setup OTP ### Extra details _No response_ ### Version Latest Stable ### PostgreSQL version _No response_ ### What were you trying to do? I'm trying to set up some integrations with the Masto API implementation. Most apps work, but I'm having a hard time with these two: - Buffer - Jetpack (from WordPress) ### What did you expect to happen? The approve button should complete the OAuth step and redirect, finishing the cycle. ### What actually happened? When I try to log in with certain integrations via the MastoAPI, I get stuck at an OAuth screen that doesn't actually let me log in. Regardless of whether the credentials are correct or not, I get the message "Incorrect Username / Password" when trying to Approve the app. ### Logs _No response_ ### Severity I cannot use the software ### Have you searched for this issue? - [x] I have double-checked and have not found this issue mentioned anywhere.

Screenshot_20240222_195230_Firefox.jpg

377 KiB

deadsuperhero added the

bug

label 2024-02-23 02:51:23 +00:00

floatingghost commented

2024-02-23 03:35:48 +00:00

Owner

sounds like those apps are handing oauth incorrectly?

not quite sure what else would be the issue, if other things work and the apps that are the only factor that changes then it sounds like it's a client issue

sounds like those apps are handing oauth incorrectly? not quite sure what else would be the issue, if other things work and the apps that are the only factor that changes then it sounds like it's a client issue

deadsuperhero commented

2024-02-23 07:14:53 +00:00

Author

I guess what's weird is that it gets all the way to the Authorize screen, but doesn't proceed beyond that? It's like there's a disconnect on who the user is?

I'll see if I can recreate it on a local setup with logs. Super weird.

I guess what's weird is that it gets all the way to the Authorize screen, but doesn't proceed beyond that? It's like there's a disconnect on who the user is? I'll see if I can recreate it on a local setup with logs. Super weird.

floatingghost commented

2024-02-23 13:57:28 +00:00

Owner

bear in mind that this error can also mean the the client passed a bad oauth application, or the redirect URL registered does not match the one used