Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Device information in LogEvent #475

Open
assurancetourix12 opened this issue Jul 22, 2024 · 5 comments
Open

Device information in LogEvent #475

assurancetourix12 opened this issue Jul 22, 2024 · 5 comments
Labels
enhancement New feature or request stale Triaged

Comments

@assurancetourix12
Copy link

assurancetourix12 commented Jul 22, 2024

Describe the feature request?

As I see in the system-log api docs, we should expect to get the field "device" in the LogEvent when listing the logs. But this field is not in the LogEvent struct (https://github.com/okta/okta-sdk-golang/blob/master/okta/logEvent.go).
Is there any reason for this or do we have any other way to get the device from the event?

New or Affected Resource(s)

The main reason for this request is, I need to identify the device that triggered the event when using Okta Verify and get the device details from the inventory.

Provide a documentation link

The expected field is described here https://developer.okta.com/docs/reference/api/system-log/#device-object

Additional Information?

When using Postman collection from okta api docs we can see this field being returned.

@assurancetourix12 assurancetourix12 added the enhancement New feature or request label Jul 22, 2024
@assurancetourix12 assurancetourix12 changed the title Device information on EventLog Device information in EventLog Jul 22, 2024
@assurancetourix12 assurancetourix12 changed the title Device information in EventLog Device information in LogEvent Jul 22, 2024
@duytiennguyen-okta
Copy link
Contributor

OKTA internal reference https://oktainc.atlassian.net/browse/OKTA-756116

Copy link

This issue has been marked stale because there has been no activity within the last 14 days. To keep this issue active, remove the stale label.

@duytiennguyen-okta
Copy link
Contributor

@assurancetourix12 do you have the response the server?

Copy link

This issue has been marked stale because there has been no activity within the last 14 days. To keep this issue active, remove the stale label.

Copy link

This issue has been marked stale because there has been no activity within the last 14 days. To keep this issue active, remove the stale label.

@github-actions github-actions bot added the stale label Nov 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request stale Triaged
Projects
None yet
Development

No branches or pull requests

2 participants