Based on the changes related to GDPR, there have been significant work done with Flexnet Publisher Toolkit to allow publisher/end users to adopt the law for GDPR.
Here is a brief of work done for the same:
1.) Debug log attributes: (Starting FNP-11.17.1) - [FNP-23218]
Usages: DEBUGLOG [+]debug_log_path [OBF_ADDMARK] [AUTO_ROLLOVER size]
The OBF_ADDMARK enables the affixing of obfuscation markers (OBF_STRT: username :END_OBF) to username in debug log.
2.) lmobfslog: New Utility introduced to generate the obfuscated Usernames for the debug log files: (Starting FNP-11.17.1) - [FNP-23039]
Thus Utility is introduced to work on below:
- Obfuscating the usernames in the debug log file.
- Removing the markers and generating original debug log file.
The lmobfslog utility processes the debug log file to generate the obfuscated usernames. It is used for debug log processing.
Note • If the debug log has been produced with OBF_ADDMARK option, only then the lmobfslog utility can generate obfuscated usernames in the debug log.
Usages: lmobfslog [-i debug_log] [-o new_debug_log] <-rmarker> Where: '-rmarker', Removes the markers from the debug log file.
3.) Reportlog: (Starting FNP-11.16.2) - [FNP-18717]
REPORTLOG specifies the report log file for this vendor daemon. It is recommended preceding the report_log_path with a + character to append logging entries; otherwise, the file is overwritten each time the daemon is started.
REPORTLOG [+]report_log_path [HIDE_User]
On Windows, path names that include spaces have to be enclosed in double quotes. If lmgrd is started as a service, the default location for the report log file is the current working directory unless a fully qualified path is specified. The optional parameter [HIDE_USER] can be specified so that any user names will be SHA2 hashed before being written to the encrypted REPORTLOG.
Update [Jan 25th, 2020]:
We have no plans to obfuscate user-name while it is being written into server logs because we feel we need this to debug any reported issues. But if companies have to ship their logs for external audit they can use this utility to obfuscate and send it outside their Org ID
Related Articles
Oracle Licenses Consumption Details and Optimizations report may fail with error in webui.log: "String or binary data woul… 4Number of Views Bad Handshake Detected Message in Server Log When Using Java API 5Number of Views Send data update job (DUJ) logs to technical support 510Number of Views How to Write Custom Messages in the DEBUG log using lc_log? 472Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Case id: 00001065
Activity: Status change: 2 hours ago