SAM - Subscription assigned field is empty

[Raau]

Hello mentors,

Since last 3 days I am facing one issue with Subscription Assigned field.

Out of 565 subscriptions, only 3 subscriptions are directly assigned. Remaining(562) are given through 2 different groups.

Now the problem is, for these 3 subscriptions, "Subscription Assigned" field is showing some value but for other 562 subscription, the same field is empty.

I have gone through the documents and found that this is the OOB behaviour. And thats the end of the research.

But still, I believe, there might be some way to get these details from okta. And that is why I came here to share this problem with you.

Please help me out with this. Any single clue will be helpful. Current job might be pulling the "subscription assigned" field value for direct users only using the API. You can suggest me the other APIs which can be used to pull this "subscription assigned" field value for all the subscriptions which are assigned through group also.

[Vikram Reddy · Accepted solution]

Hello @Raau ,

This is by design, not a bug in your job.

GET /api/v1/apps/{appId}/users
  "scope": "USER"   -> direct assignment, Okta stamps an assigned date
  "scope": "GROUP"  -> access via group push, no per-user assignment record

GET /api/v1/apps/{appId}/groups
GET /api/v1/groups/{groupId}/users

Okta only writes a per-user assignment record, and the date that goes with it, when scope is USER. Group-pushed access never gets that record because the assignment lives on the group, not the user, so whatever pulls into your Subscription Assigned field has nothing to read for those 562. Pull the app's assigned groups, expand each group's membership, and union that list with the direct USER assignments. You'll need to stamp your own assigned date for the group-derived rows since Okta won't hand you one.

Thank you,
Vikram Karety
Octigo Solutions INC