Okta
Copy Okta system-log events into the Aegis audit log.
At a glance
| Direction | Into Aegis. |
|---|---|
| What it brings in | Okta system-log events, the last 24 hours by default. |
| Where it lands | The audit log. |
| Credentials and permissions |
Either an Okta API token with the okta.logs.read scope,
or an OAuth app in your Okta organisation granted the
okta.logs.read scope (then sign in with the connector's
authorise button).
|
| Owner of imported records | Audit-log entries have no owner. |
| When it runs | On demand with Sync System Log or the API. |
| Set it up |
/connectors/okta, by people allowed to configure
connectors, on a plan that includes the connector.
|
Good to know
- When the Okta address changes after authorising, the stored token is not sent to the new address: authorise again.
Where this connects
Imported events are searched in Audit log.