Search the Community
Showing results for tags '2fa'.
Found 2 results
This change log covers what's changed in Domotz Pro service since previous Release Notes. These changes include Domotz Pro cloud, Domotz Agent and Domotz Pro App. Since previous Release Notes new versions of Domotz Agent and Domotz Pro App have been released. In order to fully exploit the new features, functionalities and bug fixes released, please make sure you have installed the latest version of Domotz Pro Mobile App: check on Apple Store or Google Play. Latest version as of today is 1.6.5 Domotz Agent: check onDomotz Portalunder the subscription tab. Latest version as per todayis 1.7.3 Violet Digital Support: check on Apple Store or Google Play. Latest version as of today is 2.6.3 Domotz Pro WebApp and Portal are already updated to the latest version January 25th, 2018 Domotz Pro App:1.6.5-Domotz Agent:1.7.3Violet2.6.3 What's new: Two-Factor Authentication:Domotz PRO userscan nowactivate Two Factor Authentication (2FA) on youraccount, and monitor the 2FA status of the Team Members Captcha protection on Violet App: aCaptcha is proposed when a user fails authentication more than 5times Alert Digest on Specific Time Window:Domotz PRO users can nowschedule anemail that summarize all triggered alerts in a specific time window of theday Demo Mode for Domotz Pro App: it is now possible to pre-view features available in Domotz Pro App/WebApp without installing a Domotz Agent or logging in with any account. The demo works on mobile even in offline mode. Improvements: Commercial Site Monitoring: removed"Home" reference from app and reports Additional Tiles: ABB Additional PDUs and Network Switches supported Ruckus Access Point specific driver (Beta Testing) Cloud improvements: faster responsiveness of the system formonitoring purposes FIX: Alert Daily Digest can nowbe configured by Team Member and Field Operator HP Switch Power Monitoring issueresolved Sonos Ethernet port statuswith multiple ethernet ports is now working properly Simultaneous Remote Connections can be enabled by leveraging the Open TCP Connection feature Known limitations: Eyes configured for deleted devices affect the total counting of Eyes Devices with multiple network interfaces (multiple MAC address) can't be merged into single device Field Operators can't set alerts on Domotz Eyes (SNMP Custom OID and TCP Services monitoring)
It would be nice to see device up/down history in the Logging report section. No need for PDF exports, simple text file would be nice. Sure, I could make sure all my alerts go to e-mail and then sort/search through those but why do that when you should be able to easily implement device up/down history. Also, login/illegal login attempts to our Domotz account should be logged (withIP of user trying to login) for auditing purposes, especially since you don't yet have 2FA. Additionally, creating an alert (push or email) would be really nice for loginand illegal login attempts. As has been mentioned in other threadse, 2FA should be prioritized. An added security measure that could easily be implemented would be a short timeout period after so many failed login attempts (5 failed attempts = 15 minute timeout or something). Going even further, the ability to blacklist/whitelist IPs for account access would be really nice.