Integrations

Integrations is the group that collects the profiles with which AGS talks to the external systems: the transfer of the identity of the verified user to the Backend Service and the monitoring of the session state of the Backend Service (Backend SSO Configurations), the alarms produced for the operator from the access statistics together with their channels (Notification Profiles), and the forwarding of the audit logs to the SIEM and syslog targets (Log Forwarding). In the AGS tab in the Configuration Menu, this group contains three screens; the left menu lists the screens in the order in the interface.

All three profiles are bound from the AGS settings of the vService: Backend SSO config and Notification profile are of a single selection, and Audit log forwarders is of a multiple selection with at most five targets. There is no built-in profile on the screens of this group.

3

Screen

In the order in the Integrations group in the interface

4

Injection type

The identity transfer to the Backend Service with Header · Basic Auth · Bearer Token · Cookie

4 + 4

Thresholds and channels

The login/MFA failure, lock and session thresholds; E-mail, SMS, SNMP, UI

5

Log targets

At most 5 syslog/SIEM targets per vService; JSON or CEF

How do the screens work together?

1. In the Backend SSO Configurations screen the identity carrying form that the Backend Service expects (a header, Basic Auth, a token, a cookie) and the session loss/logout conditions are defined; the profile is selected from the Backend SSO config field of the vService.
2. In the Notification Profiles screen the alarm thresholds and channels are defined; the profile is selected from the Notification profile field of the vService and the alarms are produced on a vService basis.
3. In the Log Forwarding screen the syslog/SIEM targets are defined; the targets are added to the Audit log forwarders list of the vService and the audit logs are forwarded in the format selected.
4. The setting canvas of the vService summarizes the profiles selected: the Corporate service sign-on box, the monitoring and notification row, the audit log targets.

Screens

Backend SSO Configurations

The identity injection to the Backend Service (Header, Basic Auth, Bearer Token, Cookie; with smart variables), the detection of the backend session loss and its strategy (a logout or a re-synchronization), the detection of the backend logout and the redirection modes.

→

Notification Profiles

The failed login/MFA rate, active lock and verified session thresholds on a vService basis; the e-mail, SMS, SNMP and interface channels; the engine state alarm and the login e-mail to the user.

→

Log Forwarding

The forwarding of the audit logs to the SIEM/syslog targets: the server, the port, UDP/TCP, the route table, the RFC 3164/5424 envelope, the JSON/CEF message, the application name; sending a test event and the forwarding limits.

→

Usage Locations

Screen	Where it is used
Backend SSO Configurations	The vService AGS settings Backend SSO config; the re-synchronization step in the flow editor; the Corporate service sign-on box on the setting canvas
Notification Profiles	The vService AGS settings Notification profile; the monitoring row on the setting canvas; the Settings → Notifications notification list
Log Forwarding	The vService AGS settings Audit log forwarders; the audit log row on the setting canvas; the common transport infrastructure with Settings → Log Transports