How to load audit_user(4) configuration data into a Native LDAP datastore
Last updated on AUGUST 01, 2016
Applies to:Solaris Operating System - Version 9 GA to 10 1/13 U11 [Release 9.0 to 10.0]
Since Solaris 11 the file audit_user(4) has become obsoleted by new configuration options in the file user_attr(4).
This document explains how the information in the audit_user(4) database (/etc/security/audit_user) can get stored and maintained in a LDAP repository to get used by LDAP Name Service clients, and provides examples for that.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms