Send Okta logs to LogPulse
The Okta System Log: sign-ins, MFA, admin changes, user lifecycle, app assignments and policy changes.
Configure → Sources → Cloud. LogPulse reads the Okta System Log API itself, without an agent. Events land in the iam index with source okta and fill the Authentication, Cloud Audit data models.Overview
- Okta System Log API to Integration poller
- Integration poller to index=iam
LogPulse signs in to Okta with the credential you give it and fetches new events every five minutes by default. You can set the interval per integration, from one minute to 24 hours.
What you need
- An Okta API token, created by an admin with the Read-only Administrator role
- In LogPulse: a role that may manage API keys. Cloud integrations fall under that right.
1. Create a credential in Okta
| Field in LogPulse | Where you find it |
|---|---|
| Okta org | The address you sign in to Okta with. The admin address (acme-admin.okta.com) works too. |
| API token | In the Admin Console: Security, API, Tokens, Create token. Create it while signed in as an admin with the Read-only Administrator role. Stored encrypted and never shown again. |
2. Add the integration in LogPulse
Go to Configure → Sources → Cloud and choose Okta. Fill in the fields, tick the data sources you want and save. LogPulse first tests the connection with your credential and tells you what is wrong when it fails.
What arrives
| Data source | Index | Source | Sourcetype | What it holds |
|---|---|---|---|---|
| System Log | iam | okta | okta_system_log | Every event of your Okta org: sign-ins, MFA, admin changes, user lifecycle, app assignments and policy changes. |
The index is the kind of data and the source is the product, so detection rules for that kind of data find Okta without changes.
Fields and data models
| Data model | What you get |
|---|---|
| Authentication | Sign-ins and MFA with user, src_ip, src_country, result and reason. |
| Cloud Audit | Admin and lifecycle changes with user, action, dest_user and object. |
Events are mapped to the data models above, with the same field names as other sources of the same kind. See field names.
The original record of Okta is kept with each event under raw, so nothing the vendor sent is lost.
3. Check the data
The first events arrive within a few minutes. Check what came in:
earliest=-1h index IN (iam) source IN (okta)
| stats count by index, source, sourcetypeThe integration page in LogPulse shows when it last read events and the last error, if any.
Troubleshooting
The connection test names what is wrong. These are the answers you are most likely to see.
| What you see | What to do |
|---|---|
| Okta refused the API token. | The token is wrong or expired, or its admin cannot read the System Log. Create it while signed in as an admin with the Read-only Administrator role. |
| orgUrl is your Okta org, e.g. acme.okta.com | Use the address you sign in to Okta with. The admin address (acme-admin.okta.com) works too. |
| The test passes but no events arrive. | Run the search above over a longer time. No results: check on the integration page that the data source is switched on and when it last read events. Okta may also simply have had nothing new. |
Frequently asked questions
- How do I send Okta logs to LogPulse?
- Add the Okta cloud integration under Configure, Sources, Cloud in LogPulse and fill in Okta org, API token. LogPulse reads the Okta System Log API itself, every five minutes by default; there is nothing to install.
- Which permissions does LogPulse need in Okta?
- An Okta API token, created by an admin with the Read-only Administrator role. Read access is enough for collecting logs.
- Which index does Okta data go to?
- The index is the kind of data: iam. The source is the product: okta. Each data source has its own sourcetype, listed on this page.
- Which data models does Okta fill?
- Authentication, Cloud Audit. Detection rules and dashboards written for a data model work on Okta without changes.