User Management 2.0
Add a User Management screen where:
1. The login activity can be viewed for a specific period of time
2. An auto "disable account" can be set after x days / months of inactivity sending a notification 3 days before
3. All relevant user data can be pulled, such as User creation date, User rights modification (with change log), User exit date.
Comments: 7
-
09 Dec, '19
Brian Berry AdminGreat idea. Please note that as of the latest November release we have partially improved this. In the Veslink IMOS Platform a new "Module Access" table, available as a join from the "User" table, is now available in the Report Designer. With this data source, you can build a report to gain visibility into permissions across users and groups. You can read more https://vesonjira.atlassian.net/wiki/spaces/help/pages/64886021/VIP+-+What+s+New.
-
13 Dec, '19
Jean-Remi LecqMay you please consider some other improvements:
4. Merge in one single place (ideally in VIP > Data Center > Security) other modules where rights are managed (like VIP > Operations > Setup > Voyage Reporting Security)
5. consider opened issues on user management (like VS-168046) in this roadmap
6. API:
a) Provide to IT capability to manage (/w renew & deletion) of the static token per user for access on API. Bulk action would be appreciated.
b) Have auhentication linked to the client' s SSO -
17 Dec, '19
Sijin JohnGood Idea!! Also it will be good if we have a delegation of authority function for a period.
Lets say for example if we want to delegate a 'Finance' personal as the 'Approval Manager Finance' for a period, this will be required to set in the system and after the period the role should automatically be removed from the user. -
13 Jan, '20
NORDEN BAAs part of User Management 2.0 we would like to see integration to IAM via AD.
-
17 Jan, '20
KaitlinAlso like the delegating authority idea!
-
15 Apr, '20
Nick JonesTo add to Andres' item "The login activity can be viewed for a specific period of time". User last login date tie is recorded. But previous login datetimes are lost - these should be retained in the database. The reason for this is that when as an application manager one wants to review user activity - 'does John/Jane need access?', knowing how frequently they log in is a key piece of data. Further this is similarly true at a lower level for use of Report designer reports.
-
14 Jun, '20
Sijin JohnAlso VIP to have the IMOS GROUP and USER access reports as was available for the desktop version of IMOS. Currently its not available and the customized report does not provide an enhanced view as was the case in desktop version.