You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Rn entry release 2024.06.0 (okta#4861)
* First pass at adding RN. WIP.
* Updated with editorial reviewed blurbs
* Commented out Redocly link for now
* OKTA-731717 - Update number of inline hooks (okta#4841)
* Update number of inline hooks per org from 50 to 100
* Update packages/@okta/vuepress-site/docs/reference/hooks-best-practices/index.md
Co-authored-by: Susan <susan.harper@okta.com>
---------
Co-authored-by: Susan <susan.harper@okta.com>
* OKTA-727230 Add new event type (okta#4817)
* Alphabetized event types and added table for new event type
* Initial data added to new event type table
* Updates as per local review
* Updates after initial review
* Updates as per editing feedback
* Updated event types and api errors page
* Update packages/@okta/vuepress-site/.vuepress/public/docs/okta-event-types.csv
Co-authored-by: grahamsmith-okta <graham.smith@okta.com>
* Fixed event-types.json to match fix Graham made in the CSV file
---------
Co-authored-by: Brian Duffield - Okta <70648001+brianduffield-okta@users.noreply.github.com>
Co-authored-by: Susan <susan.harper@okta.com>
Co-authored-by: grahamsmith-okta <graham.smith@okta.com>
"pam.project.remove_group","This event is triggered after a group is removed from a project.","2022.02.0","pam"
489
489
"pam.project.update","This event is triggered after a Project is updated. Only applicable for Okta Privileged Access. This event contains the Project name and the associated Resource Group.","2023.04.0","pam"
490
490
"pam.project_group_selector.update","This event is triggered after server selectors for a group assigned to a project are updated.","2022.02.0","pam"
491
+
"pam.resource.checkin.end","This event is triggered when a resource's check-in process completes or fails to complete. Monitor 'FAILED' outcomes of this event to identify resources that may be unavailable for checkout due to an incomplete check-in. This event contains details of the original checkout and, if a failure occurred, the reason why the check-in failed.","2024.05.1","pam"
492
+
"pam.resource.checkin.start","This event is triggered when a previously checked out resource has its check-in process started. Use this event to identify when a user's exclusive access to a resource has ended. This event contains details of the original checkout and the user who checked it in.","2024.05.1","pam"
493
+
"pam.resource.checkout","This event is triggered when a resource is checked out. Use this event to identify the exclusive access to resources. This event contains details of the resource and the user who checked it out.","2024.05.1","pam"
491
494
"pam.resource_group.create","This event is triggered after a Resource Group is created. Monitor this event to be notified when new teams in your Okta org begin using Okta Privileged Access. Only applicable for Okta Privileged Access. This event defines when a Resource Administrator has created a new Resource Group to manage resources.","2023.04.0","pam"
492
495
"pam.resource_group.delete","This event is triggered after a Resource Group is deleted. Monitor this event to be notified when a team in your Okta org stops managing access to a resource. Only applicable for Okta Privileged Access. This event defines when a Resource Administrator deleted a Resource Group.","2023.04.0","pam"
493
496
"pam.resource_group.update","This event is triggered after a Resource Group is updated. Monitor this event to be notified when Resource Group settings change. Only applicable for Okta Privileged Access. This event defines when a Resource Administrator has modified the settings for a Resource Group.","2023.04.0","pam"
"security.authenticator.lifecycle.create","Fired when an admin creates an authenticator for the org. This event can be used to identify who created an authenticator and which authenticator was created. The actor specifies the user that created the authenticator and the target specifies the authenticator name and the id. This event could also contain some authenticator specific information. Authenticator creation occurs when an authenticator is added. Related events include security.authenticator.lifecycle.update.","2022.06.0","authenticator","event-hook-eligible","oie-only"
582
585
"security.authenticator.lifecycle.deactivate","Fired when an admin deactivates an authenticator for the org. This event can be used to identify who deactivated an authenticator and which authenticator was deactivated. When fired, this event contains information about the authenticator type that was deactivated and the actor who deactivated the authenticator. Authenticator deactivation occurs when an authenticator is removed. Related events include security.authenticator.lifecycle.activate.","2020.06.3","authenticator","event-hook-eligible","oie-only"
583
586
"security.authenticator.lifecycle.update","Fired when an admin updates an authenticator in the org. This event can be used to identify who updated an authenticator and which authenticator was updated. The actor specifies the user that updated the authenticator and the target specifies the authenticator name and the ID. There may be a second target with details of any authenticator method updates. This event could also contain authenticator specific information. Authenticator update occurs when an authenticator is edited. Related events include security.authenticator.lifecycle.create.","2022.06.0","authenticator","event-hook-eligible","oie-only"
587
+
"security.breached_credential.detected","A credential, such as a password, which is associated with a known breach was used during an authentication flow. Used to identify users for whom credential rotation or other risk mitigation is necessary. The actor is the user with the breached credential. For Identity Engine, a target will indicate the specific credential associated with the breach. The outcome for this event will always be SUCCESS with a severity level of WARN. If breached credential protection is enabled, auser.session.clear will also be fired. These two events can be correlated by the Request ID.","2024.04.2","account","event-hook-eligible","security","user"
584
588
"security.device.add_request_blacklist_policy","Added request blacklist to request blacklist policies.","2018.08","device","security"
585
589
"security.device.remove_request_blacklist_policy","Removed request blacklist from request blacklist policies.","2018.08","device","security"
"user.authentication.slo","User single logout out (SLO) from app.","2016.11","user"
839
843
"user.authentication.sso","Fired when a user performs a single sign-on (SSO) to an app instance and contains the client details of the user. Can be used to identify when a user attempted to sign into an application for audit or debugging purposes. Note that the event is fired even when the sign-on is unsuccessful.","2016.11","event-hook-eligible","user"
840
844
"user.authentication.universal_logout","This event is fired when an admin or system account triggers Universal Logout against an app instance. It contains the app instance details for which the Universal Logout API was fired. This event identifies when applications have had Universal Logout triggered for audit or debugging purposes. This event is only fired once. It's only fired for applications that have been configured for Universal Logout. You can configure it under Risk policy, Continuous Access policy, or in an admin-initiated Clear User Session.","2024.02.2","event-hook-eligible","session","user"
845
+
"user.authentication.universal_logout.scheduled","This event is fired when an admin manually triggers Universal Logout for a user. It contains context about the initiating request, such as where the request originated and how the Universal Logout endpoint was invoked. After Universal Logout is complete, the user.authentication.universal_logout event is fired, and you can correlate both events using the traceID. This event identifies the geolocation, IP address, and IP chain of the requesting entity. This event is only fired once. You can correlate this event with the user.authentication.universal_logout event using traceID.","2024.06.0","event-hook-eligible","session","user"
841
846
"user.authentication.verify","Verify user identity.","2017.27","end-user-visible","user"
"user.identity_snapshot.attestation.create","Create identity snapshot attestation for a user. This event can be used by administrators to audit identity snapshot attestations minted for a user. The user and the application are in the event, signifying which user the attestation token is being minted for, and which application is requesting it.","2020.09.3","attestation","user"
"user.risk.change","Indicates a user's risk level has changed. This can be used to monitor risk level changes for users. This event is fired when Okta determines that a user is associated with activity or context that indicate risk.","2023.01.2","event-hook-eligible","risk","security"
"user.session.clear","Clear user session.","2016.15","event-hook-eligible","session","user"
868
-
"user.session.context.change","User session context changed. This event indicates that the context in which the session is being used has changed significantly enough from the context in which the event was created, that re-evaluation of policy may be required. Often this indicates a security issue related to the session.","2023.01.0","session","user"
873
+
"user.session.context.change","User session context changed. This event indicates that the context in which the session is being used has changed significantly enough from the context in which the event was created, that re-evaluation of policy may be required. Often this indicates a security issue related to the session.","2023.01.0","event-hook-eligible","session","user"
869
874
"user.session.end","User logout from Okta.","2016.02","event-hook-eligible","session","user"
870
875
"user.session.expire","Expire user session. This event does not appear in the system logs unless the user explicitly signs out or the user session is revoked by an admin.","2016.15","session","user"
0 commit comments