#dominoforever | Product Ideas Portal

 

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Show account activity - which app. location and ip logged in to your Web or Notes account?

When I login as a Dominouser I want to be able to see when and where my last logins was made, and from what client/app

Currently I have no control of my account. I have no idea if someone else managed to login to my account through web, smtp, ldap, imap, pop3 etc. (the same goes for the Notes ID file)

Have a look at gmail, they provide all login activities of what client , ip adress, approx location and time/date.

This information should be available to see by the logged in user and not something that is hidden for only administrators.

  • Guest
  • Jan 19 2019
  • Needs review
  • Attach files
  • Guest commented
    20 Jan, 2019 10:40am

    Daniel Nashed:

    It might not be that easy to get it implemented for all protocols.
    And it will be difficult to have one place.

    But yes I fully agree! We had the request already for web login.
    Users want to see the failed and last login at login time after they login.

    I like the idea of a central page like the $preferences.nsf!

    When I really think about it, this would be local to one server only.

    Having a way to push login and failed attempts to a central place that aggregates them, would be easier to implement and would show information for all servers.

    It could be implemented similar to the new statistics publishing.

    Have a MQ to push the login/failed password information to a central thread in the server process and have that server process push the info to a central place.

    That would allow all type of security applications to use it.
    And we could have a Domino database that could be the consumer of the REST requests by default...

    See my blog post for details --> http://blog.nashcom.de/nashcomblog.nsf/dx/domino-10-statistic-collection.htm

    -- Daniel

  • Guest commented
    19 Jan, 2019 03:33pm

    one idea is to make a page for users that applies to the whole server,  something similar to the  http://hostname/$Preferences.nsf?OpenPreferences