Package io.meeds.social.security.service

Class AccountDeletionService

java.lang.Object
io.meeds.social.security.service.AccountDeletionService
@Service public class AccountDeletionService extends Object
Executes the account deletion requests recorded by AccountDeactivationService, once their grace delay elapsed. This service starts no transaction on its own: the caller (the job) owns the container lifecycle, and the batch commits one transaction per processed account — marker removal and deletion together — so the processing stays idempotent without any cluster lock: a concurrent or replayed run finds no marker once an account's transaction is committed, and the deletion itself (social identity soft-deleted then IDM user removed, mirroring the users administration deletion) is a no-op once the IDM user is gone.

  • Field Summary

    Fields
    Modifier and Type
    Field
    Description
    static final String
    ACCOUNT_DELETED_EVENT
     

  • Constructor Summary

    Constructors
    Constructor
    Description
    AccountDeletionService()
     

  • Method Summary

    Modifier and Type
    Method
    Description
    List<String>
    collectPendingRequests()
     
    void
    deleteAccount(String username)
    Deletes the account the way the users administration does: the social identity is soft-deleted first, then the IDM user is removed without broadcast — this ordering prevents any concurrent by-username resolution from resurrecting the deleted identity while the IDM user still exists.
    boolean
    prepareDeletion(String username)
    Re-checks the eligibility of one recorded request and, when the account has to be deleted, removes the request marker — committed together with the deletion in the per-account transaction controlled by the caller — so a replayed run finds nothing to do.
    void
    processPendingDeletionRequestOf(String username)
     
    void
    processPendingDeletionRequests()
    Processes all the recorded deletion requests: collects the pending requesters first (the enumeration must not be paged over while its rows get deleted), then handles each account independently so one failure never prevents the other deletions.

    Methods inherited from class java.lang.Object

    clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

  • Field Details

  • Constructor Details

    • AccountDeletionService

      public AccountDeletionService()

  • Method Details

    • processPendingDeletionRequests

      public void processPendingDeletionRequests()
      Processes all the recorded deletion requests: collects the pending requesters first (the enumeration must not be paged over while its rows get deleted), then handles each account independently so one failure never prevents the other deletions. The current transaction is committed and reopened after each account, so the batch never accumulates one big transaction and a mid-batch failure never rolls back the already processed accounts.

    • processPendingDeletionRequestOf

      public void processPendingDeletionRequestOf(String username) throws Exception
      Throws:
      Exception

    • collectPendingRequests

      public List<String> collectPendingRequests()

    • prepareDeletion

      public boolean prepareDeletion(String username) throws Exception
      Re-checks the eligibility of one recorded request and, when the account has to be deleted, removes the request marker — committed together with the deletion in the per-account transaction controlled by the caller — so a replayed run finds nothing to do. The marker is also cleaned up for requests that can never execute anymore (revoked by an admin re-activation, user already gone, externally synchronized account or unreadable marker). Deliberately not re-checked: the admin deletion option — the request was confirmed by its user under an enabled policy, turning the option off only prevents new requests.
      Returns:
      true when the account deletion must proceed
      Throws:
      Exception

    • deleteAccount

      public void deleteAccount(String username) throws Exception
      Deletes the account the way the users administration does: the social identity is soft-deleted first, then the IDM user is removed without broadcast — this ordering prevents any concurrent by-username resolution from resurrecting the deleted identity while the IDM user still exists. The user content (activities, comments, documents...) is preserved by design and keeps being displayed.
      Throws:
      Exception