User History Cleanup - Revision history

MaryH at 19:30, 9 April 2018

2018-04-09T19:30:45Z

← Older revision		Revision as of 19:30, 9 April 2018
Line 3:		Line 3:
	Likewise, when users log into the Globalyzer Client (Workbench, CLI, Lite if configured to do so, or the Globalyzer Maven Plugin) and execute scans, that login and scanning history is stored on the Server.		Likewise, when users log into the Globalyzer Client (Workbench, CLI, Lite if configured to do so, or the Globalyzer Maven Plugin) and execute scans, that login and scanning history is stored on the Server.

	Administrators and Managers can view and delete this data on the Server by ~~select~~ Cleanup User History from their home page.		Administrators and Managers can view and delete this data on the Server by selecting Cleanup User History from their home page.

	Additionally, a cron job runs nightly to remove data. Our hosted server is configured to keep data for 90 days. If you install your own Enterprise Server, this value is configurable via the gzserver.cleanup.daysToKeep setting in the GzserverConfig.groovy file. If not configured, it defaults to 90 days.		Additionally, a cron job runs nightly to remove data. Our hosted server is configured to keep data for 90 days. If you install your own Enterprise Server, this value is configurable via the gzserver.cleanup.daysToKeep setting in the GzserverConfig.groovy file. If not configured, it defaults to 90 days.

MaryH at 19:29, 9 April 2018

2018-04-09T19:29:53Z

← Older revision		Revision as of 19:29, 9 April 2018
Line 1:		Line 1:

	When users login to their Globalyzer Server accounts, that login history is stored on the Server.		When users login to their Globalyzer Server accounts, that login history is stored on the Server.
	Likewise, when users log into the Globalyzer Client and ~~executed~~ scans, that login and scanning history is stored on the Server.		Likewise, when users log into the Globalyzer Client (Workbench, CLI, Lite if configured to do so, or the Globalyzer Maven Plugin) and execute scans, that login and scanning history is stored on the Server.

	Administrators and Managers can view and delete this data on the Server by select Cleanup User History from their home page ~~on the Server~~.		Administrators and Managers can view and delete this data on the Server by select Cleanup User History from their home page.

	~~To keep this data from overwhelming the Server~~, a cron job runs nightly to remove data. Our hosted server is configured to keep data for 90 days. If you ~~installed~~ your own Enterprise Server, this value is configurable via the gzserver.cleanup.daysToKeep setting in the GzserverConfig.groovy file. If not configured, it defaults to 90 days.		Additionally, a cron job runs nightly to remove data. Our hosted server is configured to keep data for 90 days. If you install your own Enterprise Server, this value is configurable via the gzserver.cleanup.daysToKeep setting in the GzserverConfig.groovy file. If not configured, it defaults to 90 days.

MaryH: Created page with " When users login to their Globalyzer Server accounts, that login history is stored on the Server. Likewise, when users log into the Globalyzer Client and executed scans, that..."

2018-04-09T19:16:57Z

Created page with " When users login to their Globalyzer Server accounts, that login history is stored on the Server. Likewise, when users log into the Globalyzer Client and executed scans, that..."

New page

When users login to their Globalyzer Server accounts, that login history is stored on the Server.
Likewise, when users log into the Globalyzer Client and executed scans, that login and scanning history is stored on the Server.

Administrators and Managers can view and delete this data on the Server by select Cleanup User History from their home page on the Server.

To keep this data from overwhelming the Server, a cron job runs nightly to remove data. Our hosted server is configured to keep data for 90 days. If you installed your own Enterprise Server, this value is configurable via the gzserver.cleanup.daysToKeep setting in the GzserverConfig.groovy file. If not configured, it defaults to 90 days.