
6qo9p (6qo9p) asked a question.
Hey, I am working on a script which list certain users of my org and perform some action on them in my app.
For using okta api, I dont want to use SSWS api token but build an Auth token using client ID and secret.
Searched for the curl for it and it looks like it requires a scope field.
For that I made a custom scope (read.users) for the default authorization server but not sure how to give it permissions for listing users. It gives out 401 with the generated session token.
Also how is it different from generic okta.users.read scope and what all other tokens can be generated for this use-case?

Hello @6qo9p (6qo9p) Thank you for reacting out to our Community!
You need to add access policy to your authorization server, please see article below:
https://developer.okta.com/docs/guides/customize-authz-server/main/#create-access-policies
Additionally if you need further assistance we recommend to leverage the Okta Developer forums for this type of questions and take advantage of their expertise.
https://devforum.okta.com/
--
Subscribe Today: The Okta Community is on YouTube