Requirements for this issue:

• At Admin UI make sure that both Close and Suspended actions are provided
• At RC side, make sure when an account is Suspended all of his resources are not deleted but deactivated for example:
  • Account and Sub-Accounts cannot login.
  • Unable to register clients
  • Deny calls to DIDs
• When account goes back to Active state, re-enable the resources.

Hi @gvagenas , can I start investigating and do the implementation for this enhancement?

Hi @gvagenas , when an account is Suspended, all of his Sub-Accounts will be Suspended too and when his account is activated then all of his Sub-Accounts will be activated accordingly.

But what if one of his Sub-Accounts was already in Suspended state before. If his account is suspended then activated so the already suspended sub-account will be activated too.

In my opinion, we should keep the already suspended sub-account not change. I think that we should add one column in database as in below to save the previous state of an account.

When an account is from Active to Suspended:

1. Its effective state & previous state will be set to Suspended
2. Copy sub-accounts' effective state to previous state
3. Set sub-accounts' effective state to Suspended

When an account is from Suspended to Active:

1. Set its effective state & previous state to Active
2. Copy sub-accounts' previous state to effective state

@ddhuy if I understand correctly what @gvagenas had in mind, we would not have to change the status of the sub-accounts themselves.

the requirement he has listed (that "Account and Sub-Accounts cannot login") can simply be implemented in our authorization logic.

this way, when we have to decide if a user is allowed to login, we can add the additional check of whether (one of) their parent accounts is SUSPENDED.

This way, we don't have to modify status of sub-accounts.

@gvagenas wdyt?

@gsaslis , Thank you for the explanation. I understand it now so I will continue with the implementing.