I was aware of these endpoints but it would mean an additional call to Okta (besides possible ways of caching).
The use case I have is: users need to be able to run api calls on servers that are headless and there can’t be user interaction when the scripts run. I am looking at a possible scenario of having 1 client per user and I am exploring how I can set a custom property of a client with the username of the user.
Do you know if this is possible without making another call to Okta to find out what user is linked to an application?
Can you please open a support ticket with us at developers@okta.com in order to have a screen sharing meeting and discuss further about this implementation?