Skip to content

Auth: Handle invalid account #2865

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

Merged
merged 12 commits into from
Jul 2, 2025
Merged

Conversation

DaVinci9196
Copy link
Contributor

@DaVinci9196 DaVinci9196 commented Apr 22, 2025

#2731 (comment)
Based on @fynngodau’s solution, use notifications to inform users whether their account has expired. Users can choose to log in again or log out.
Choosing to re-login will be handled based on the newly added reauth interface.

@lucasmz-dev
Copy link
Contributor

Nice! Great to see this fixed 😭😭😭

Copy link
Member

@fynngodau fynngodau left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Many thanks for implementing this feature. However, as a regression, the UserSatisfyRequirements resolution feature no longer works with these changes.

@fynngodau
Copy link
Member

One thing I noticed is that reauth is not possible if Android ID has changed (i.e. when microG data has been deleted, but accounts were kept). This should be relatively easy to fix, but I don't think it needs to be solved in this PR. 🙂

@fynngodau
Copy link
Member

When testing this PR, I removed some specific devices from the Security tab in myaccount. A few days later, unrelated to this PR, I was not able to sign in (or reauth) from microG until I changed Android ID; perhaps the device was locked out in a way microG is unable to recover from? The server response was only a generic error.

Copy link
Member

@fynngodau fynngodau left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the improvements. Reauth and enterprise setup both work at the same time now. 👍

I'm not entirely happy with the UI choices made for the notification, but that's for @mar-v-in to decide.

@mar-v-in mar-v-in added this to the 0.3.8 milestone May 27, 2025
@mar-v-in mar-v-in force-pushed the fix_account_invalid branch from bbb42a5 to ce73cce Compare July 2, 2025 09:51
@mar-v-in mar-v-in merged commit b9b7c06 into microg:master Jul 2, 2025
1 check passed
@DaVinci9196 DaVinci9196 deleted the fix_account_invalid branch July 14, 2025 01:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

microG does not behave gracefully with invalid sessions of Google accounts
5 participants