V20 unable to change or view passwords for users w/o email, potential functionality flaw?

[SRQCompServices]

We recently set up a new V20 instance for a client (self-hosted in the cloud) but encountered an issue that seems like it might be a potential functionality flaw in V20.

The client does not use email addresses for any employees or extensions; the 3CX users are simply un-named extensions, such as Front Desk 1, Front Desk 2, etc., with no email addresses associated with them, except for our admin account.

It appears that the ability to set In-Office and OOO statuses has been removed from V20, as the *791, *792, etc., no longer work via BLFs on the phone. As a result, we now need to give office managers the ability to log in to the web client to manually open or close the office. However, there doesn't seem to be an option to view or control what their password is reset to without an email address linked to their extension. The reset button doesn't appear to actually have any function without an email tied to the extension.

Is 3CX V20 functionality entirely dependent on using email addresses, or is there another way to reset a user's password to a predefined one?

 

[SteveITS]

3CX moved passwords to the user. And tied logins to email. Extensions without an email cannot log in.

This may help with office hours: https://www.3cx.com/docs/call-api-linux/#h.nx3a0hqytc3w

 

[NicholasP_3CX]

The email address is now a mandatory requirement for a user to have access to the web services of 3CX.

The email address is now considered as a unique identifier for the functioning of the 2FA as well, so these will need to be unique.

The Emergency code for putting the PBX in or out of office hours forcefully has been removed by default due to potential clashes with each department having their own office hours. If you still wish to do this at the global level you can use the link provided above. However, do note that this is an all or nothing. To maintain complete control over each department, the web client is the way to go.

The passwords can be reset by the users themselves, releasing the chore for the admin to have to reset the users passwords. You could also utilise the SSO capabilities via the Google and Microsoft integrations.

Not a functionality flaw at all, just a focus on security and flexibility.

 

[SRQCom]

The email address is now a mandatory requirement for a user to have access to the web services of 3CX.

The email address is now considered as a unique identifier for the functioning of the 2FA as well, so these will need to be unique.

The Emergency code for putting the PBX in or out of office hours forcefully has been removed by default due to potential clashes with each department having their own office hours. If you still wish to do this at the global level you can use the link provided above. However, do note that this is an all or nothing. To maintain complete control over each department, the web client is the way to go.

The passwords can be reset by the users themselves, releasing the chore for the admin to have to reset the users passwords. You could also utilise the SSO capabilities via the Google and Microsoft integrations.

Not a functionality flaw at all, just a focus on security and flexibility.

Thank you for the prompt response, it seems like V20 might not be the best fit for us and we might look at rolling back to v18 until such time as v20 meets our needs. Other critical missing features such as the ability to edit multiple extensions at once are also a large pain point.

Do you know if 3CX is still planning to discontinue support for v18 at the end of 2024 or might that be extended until such time as V20 reaches feature parity with v18?

 

[SteveITS]

Multi-edit is in the update 3 Alpha version so it's coming.

I highly doubt 3CX will keep updating certificates etc. on v18. They've been pretty clear when things will stop working.

Rollback is an entirely different question, since once a "license key is upgraded to v20" there isn't a path backwards.