Working with a massive DS server database, it is all Additional Claims Audit data. What is this? I thought DS was only for user accounts and application licensing.
The audit data is stored on disk. What is stored in the database is for reporting purposes only. It is similar to repository auditing: write to disk, then load into database for reporting, but the loading is automatic and not as customizable.
To adjust how much data is stored in the database itself, you can change the "audit trimming" settings.
You can read more in the help files:
Claims are a part of identity management, i.e. what the subject is or is not, so I imagine the claims audit data would probably relate to authentication activity.
For example, in .NET things like surname, email, etc. fall under the umbrella of System.IdentityModel.Claims and they provide information about the user.
Well they dont use DS Auth so there are no users besides licenses assigned.
Jason is correct: these are about user profile information. It's not limited by whether or not the user authenticates through LFDS nor what type of user they are.
If you are saying that all users are either in the repository or on the Forms server, there are still calls to LFDS during user authentication for active directory and LDAP users, even if they aren't authenticating through the LFDS SSO page.
Finally, LFDS administrators are added automatically to the LFDS page, so they also have claims information that would be audited when the user is first added and sometimes on later login.
If the amount of data is an issue, you can adjust what events are auditing on the auditing configuration page.
If you are not using LFDS auditing, you can simply turn the feature off to stop the logging completely.
Oh ok, how can we store this data on the disk and or manage the retention? All of our other audit data is stored ont he disk.
The audit data is stored on disk. What is stored in the database is for reporting purposes only. It is similar to repository auditing: write to disk, then load into database for reporting, but the loading is automatic and not as customizable.
To adjust how much data is stored in the database itself, you can change the "audit trimming" settings.
You can read more in the help files:
Got it, we are trimming it down. Not sure this customer even needs it, they have Audit Trail.