Safeguard Reference Manual (G06.29+, H06.08+, J06.03+)

Event-Exit-Process Commands
Safeguard Reference Manual — 520618-030
15 - 28
Processing of Authorization Requests
disabled, then the deniable user waits indefinitely for a response from the event-exit
process. The requestor process (including the entire thread), initiating the authorization
check, will hang.
Other Error Handling for Authorization
Other problems that cause timeout behavior are I/O errors, disabling of the event exit,
and invalid data received from the event-exit process.
I/O errors can occur when the event-exit process halts before responding to a request,
or when it is enabled but is down or restarting and the open is incomplete. In either of
these events, the request is resubmitted to the event-exit process once the open is
established. However, the timer is still running on these requests, and a timeout is
likely to occur. EMS messages will be sent to identify these errors.
If the event-exit process is disabled while a request is pending, the request is allowed
to complete, providing it does so within the timeout interval. If a timeout occurs and the
request is from a deniable user, a ruling of NORECORD and a status of NOLINK is
returned to PROTECTION_CHECK_. If a timeout occurs and the request is from an
undeniable user, a ruling of YES is assumed, and the access attempt is allowed to
proceed, subject to a Safeguard access check.
If invalid data is returned in a reply from the event-exit process, an EMS message is
sent to identify the problem. If the request is from a deniable user, a ruling of
NORECORD and a status of NOLINK is returned. If the request is from an undeniable
user, a ruling of YES is assumed, and the access attempt is allowed to proceed,
subject to a Safeguard access check as described in Processing of Authorization
Requests on page 15-26.
Warning Mode Interaction
Safeguard warning mode has no effect on rulings made by the event-exit process.
Warning mode rulings are applied only after the event-exit process has ruled and the
SMON performs a subsequent access check. For example, if warning mode is in effect
and the event-exit process denies access, the access attempt is denied. If warning
mode is in effect and the event-exit process grants access, but the SMON denies
access, the access is allowed because of warning mode. For more information about
warning mode, see the Safeguard Administrator’s Manual.
Auditing of Authorization Events
If the Safeguard software is configured for auditing of the object being accessed, audit
records are generated for access attempts on that object when Safeguard is involved
in the ruling.
Note. The TIMEOUT-ALL-AUTHZREQ attribute is supported only on systems running H06.26
and later H-series RVUs and J06.15 and later J-series RVUs.