-
Notifications
You must be signed in to change notification settings - Fork 593
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
/devices is missing info on getting users, etc #3789
Comments
Thanks, Gabriel. Will review and get back to you on this one, too. |
also missing info on
etc EDIT: added |
Logged internal ticket to address: https://oktainc.atlassian.net/browse/OKTA-567622 |
Any news on this? |
Assigned it to another writer. Let me check. |
Any news? |
Hi Gabriel, Unfortunately, just in the backlog, I think. The monthly release is taking precedence at the moment; hopefully, after that. Brian |
Hi @gabrielsroka , I've chatted with the Devices team (some of whom remember you from your Okta days). They wonder if the following operation handles your use cases: https://developer.okta.com/docs/reference/api/devices/#usage-example-expand-user If not, please let us know what's missing. We do realize that we should doc the following:
I look forward to hearing from you, Brent |
Your link expands users for all devices. My example is for one specific device. I think both of useful.
I don't know. I'm reverse engineering the API by using the UI. It seems better to ask the engineers what's in the API so we can document it. |
Hi Gabriel, The new operation is live on the "old" docs site: https://developer.okta.com/docs/reference/api/devices/#list-all-users-for-a-device And will be live on the new redocly site in a few days (it'll appear at the bottom of the list of operations in the left nav): https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Device/ I know we still need to capture the details of the |
it doesn't seem to paginate, nor accept the |
Okay... following up. Sorry for the delay. |
hi again, this came up again today. i opened this issue in Dec. do u have an ETC? |
Hi @gabrielsroka , are we now able to close this issue? Thank you again for your patience. |
Waiting on this |
Hi @gabrielsroka , can you please review this List Devices reference? |
|
also need devices for a given user |
Sorry @gabrielsroka , I got ahead of myself, the For your other questions:
|
i confirmed userSummary works in preview. thanks.
what do you mean "not supported"? i tried it. it works. it's how the UI does it, too. did u try it?
i'm not sure what you're referencing here. |
Note that
When I try this request, I don't get anything meaningful. But going by the reference docs,
I thought one of your questions was about using search on
I can't find documentation on this endpoint (it's probably not supported). Nevertheless, I'll open a doc query into this endpoint to confirm. Thanks for your patience while we migrate to the OpenAPI spec. |
this is what the UI does [1] [2] Okta customers need this functionality via the API, too (not just the UI). since it's undocumented but easily discoverable, i'm asking for it to be documented since it's useful and necessary.
I'm not a customer. i'm trying to help customers who are asking for this stuff.
again, the UI does this. customers need it. it's a public (but undocumented) api. i'm asking for it to be documented. |
note what was said in the above 2 comments by @brentschaus-okta
|
@gabrielsroka Thanks for calling this out and for your patience working through the issue here! I think our best approach from this point is to both work with CSMs and support to engage with internal teams and also log some Okta Ideas to reflect the behavior you need and get support from the larger community. This will provide better justification for this request. Thanks again! |
any update on this @brentschaus-okta , et al? it's been 18 months. yet another Okta customer asked for this. |
Hi Gabriel, this was left in the Engineering and PM's court as last I recall. Let me re-engage with the team. |
https://developer.okta.com/docs/reference/api/devices is missing info on getting users (and perhaps other related collections)
to get a device's users:
GET /api/v1/devices/${deviceId}/users
this would be analogous to getting a group's users:
GET /api/v1/groups/${groupId}/users
which is documented here: https://developer.okta.com/docs/reference/api/groups/#list-group-members
The text was updated successfully, but these errors were encountered: