helpdesk
helpdesk copied to clipboard
[INFRA-2851] Add "Delete account" to accounts.jenkins.io
I want to delete my account, but I cannot do so anywhere.
Originally reported by petoknm, imported from: Add "Delete account" to accounts.jenkins.io
- status: Open
- priority: Major
- resolution: Unresolved
- imported: 2022/01/10
HI Peter Majchrak,
I agree with you that it's an important missing feature in our infrastructure.
We are currently working to deprecated our old account application "https://accounts.jenkins.io" from here in favor of Keycloak "https://beta] .accounts.jenkins.io" normally keycloak which should soon allow it [link|https://issues.redhat.com/browse/KEYCLOAK-953. Meanwhile I am going to delete your account myself
Hello, I tried to connect to the beta version but still no Delete account found, although KEYCLOAK-953 is marked as implemented. How can I delete my account?
I would love to work on this issue
I would love to work on this issue
I think that this is part of this discussion: https://github.com/jenkins-infra/helpdesk/issues/2232
I read the discussion you mentioned, and as I understand, there were plans to replace the existing authentication system with Keycloak. I don't think the account app uses KeyCloak right now. Also, this PR was just closed and not merged: https://github.com/jenkins-infra/kubernetes-management/pull/259. So, is there something I am missing?
"just closed"... in 2020 already.
I would suggest looking at other issues than the ones related to account app for now.
Okay, thanks
Closing in favor of #2232
Is there a reason to close this as keycloak et all don't seem to be worked on right now?
There's no harm in someone implementing this as it reduces the workload that is done on the helpdesk.
Is there a reason to close this as keycloak et all don't seem to be worked on right now?
There's no harm in someone implementing this as it reduces the workload that is done on the helpdesk.
We discussed it during the last Jenkins Contributor Summit on FOSDEM, and the risk of a bug deleting the LDAP data was considered high compared to the need to change to keycloak. That is the reason why we closed to streamline the effort.
However you are correct and we can reconsider with no problem, but it is clearly not a newcomer easy issue
Can I work on this?
Can I work on this?
Please choose another task. Even if the issue is kept open, we want to avoid the deletion to be implemented in accounts.jenkins.io as deploying this change in a safe manner would be too costly on the infra team compared to switching to keycloak