Duplicate of my request ZBXNEXT-4966

Actually the other ticket was from 2014 so this was the duplicate 

we lost 36 votes now and got 7 votes in place 

so now this feature has less chance to get implemented  soon unless we find a sponsor

Its 2023 and Zabbix does not have native MFA functionality

Hi to all,

hope that zabbix team consider to prioritize 2FA out of the box.

Wen i see this feature request priority marqued as minor,  make me think what kind of perspective is put on zabbix data security.

Really hope that someone on zabbix team can push this.

Best regards.

We all want to have all our insights to be found in centralized Zabbix. But the gain is there also for hackers.
One of the most used attack vectors is based on valid credentials (at least in 2022 based on data from Cisco Talos). 

I was surprised not to find the most easy 2FA method (OTP standard like Google Authenticator is using) being implemented (yes there is a fork that adds this, but I think most of us don't want to become dependent on yet another party). As this is well-known code, I would guess that it would not take much effort to add this feature?

There is a great chance we will be able to include it into Zabbix 7.0, working on business level requirements currently.

+1

Can't believe how few votes this has gotten yet. I hope it will be added soon because hacking it in would be a nightmare. 

+1

I think it's worth adding MFA to Zabbix. I believe that Zabbix is ​​quite a critical place in the company's infrastructure, even though it does not have to be exposed to the Internet.

Status resolved, Resolution unresolved 🧐

This is intended, the Resolution is set when the Status is Closed.

Hmm, regarding previous 2 comments, it seems that some administrative work needs to be done

• From the FixVersion it seems that this is implemented for new versions. Great a big thank you! We'll be surely going to use this.
• ZBXNEXT-4966 is clearly a duplicate, but it's status is 'Open' and not linked as duplicate?
• How is it possible that there are 3 dependencies, where 1 is still open? Then this one would not be a dependency I guess?
• If this is implemented in new code, then the resolve status should not be Unresolved, but Resolved as it is implemented.

Just trying to assist in having clear communication towards the community...

Yes, we know ZBXNEXT-4966 is the original ticket but for some reason it was decided to take this one and start implementation using its reference number. I didn't want to close the ticket of starko because of the respect and votes. But at this point it looks like it brings more confusion so I'll close it.

Once again, the ticket has Status and Resolution. The latter is an additional information for some of the options of Status. Now "Resolved" Status has no additional information, it means the implementation is ready and now we are waiting for QA. What you are looking for is Status "Closed" and Resolution "Fixed". That would mean the issue is complete.

Thanks for the info @dimir. I'm used within Jira to not see any Resolution value until the status become resolved or closed. Then this will prevent unlogic situation like status=resolved, with resolution=Unresolved. But anyway I understand your executed logic. Basically it's saying: "Don't look at the resolution until the status=Closed".

Correct, yeah. I have also seen it differently in other projects but this is how things are in this one.

Available in:

• 7.0.0beta2 (master) 5da9236b0c4, 0139a5fbe67

Documentation (7.0) updated:

• Introduction > What's new in Zabbix 7.0.0
• Installation > Best practices > Web server (updated note)
• Installation > Web interface installation (added curl as a pre-requisite)
• Configuration > Users and user groups > User groups (updated configuration screenshot and parameters)
• Web interface > Frontend sections > Users > Users (updated user list screenshot and mass editing options)
• Web interface > Frontend sections > Users > Authentication (updated configuration screenshot and list of authentication methods)
  • HTTP, LDAP, SAML (updated configuration screenshots)
  • MFA (added new page)

• API > Appendix 2. Changes from 6.4 to 7.0 (added new mfa API; updated authentication, user, usergroup APIs)
• API > Method reference:
  • Authentication > Authentication object (added new properties) and authentication.get (updated example)
  • MFA (added new API)
  • User > user.login (updated note, return values, and example)
  • User group > User group object (added new properties) and usergroup.get (added new parameters and updated example)