Skip to content
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

EA: The app should hide account deactivation in OIDC-aware mode #8619

Closed
pmaier1 opened this issue Aug 21, 2023 · 3 comments · Fixed by #8627
Closed

EA: The app should hide account deactivation in OIDC-aware mode #8619

pmaier1 opened this issue Aug 21, 2023 · 3 comments · Fixed by #8627
Assignees

Comments

@pmaier1
Copy link

pmaier1 commented Aug 21, 2023

In a native OIDC environment, account deactivation does not work anymore via /account/deactivate. For this reason, the feature should be hidden in the UI according to MSC2964.

Screenshot from Web to make this more clear:

image

@bmarty @hughns

@bmarty bmarty self-assigned this Aug 22, 2023
@bmarty
Copy link
Member

bmarty commented Aug 22, 2023

@pmaier1 should the UI be hidden, or should it opens the account manager on a specific page?
I prefer to get a confirmation, since Google policy require the app to have a way to deactivate accounts.

@pmaier1
Copy link
Author

pmaier1 commented Aug 22, 2023

Hmm, we generally decided to hide it as there already is a way/button to "manage account" in OIDC-aware mode that would guide you to the MAS web UI (which will offer account deactivation at some point in time). Not sure whether this is an issue for the Google policy.

@bmarty
Copy link
Member

bmarty commented Aug 22, 2023

OK, this is OK to remove the button then. I can quickly do it.

@hughns hughns changed the title The app should hide account deactivation in OIDC-aware mode EA: The app should hide account deactivation in OIDC-aware mode Sep 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants