
ShivankA.33244 (Customer) asked a question.
I want to configure okta to my scim api and I am following https://developer.okta.com/docs/guides/scim-provisioning-integration-connect/main/
When I choose Oauth2.0 template and go to the provisioning tab, I can see only option to add token and base url.
I want to ask how can I add my authorization endpoint which takes client id and secret and gives the token back ?

Hi @ShivankA.33244 (Customer),
Thank you for posting on the Okta community page!
I am not sure I have fully understood your inquiry, but I have done some research and I have managed to find the bellow articles related to your question that might help you achieve your use case:
Additionally, my recommendation would be to leverage the Okta Developer forums for this type of questions and take advantage of their expertise.
On another note, the Okta Community Catalysts Program is now live. Collect online badges when you participate in the Okta Help Center Questions community. Learn more here.
Hi @flaviu.vrinceanu1.5628408972654734E12 (Customer Success Service Delivery)
Let me give you more details around my usecase.
I want to do SCIM user provisioning using OKTA wherein I have SCIM user apis ready and I want that if a user exists in okta then the same user should get created in my application using my SCIM user api.
For that, I have a question regarding authorization flow. When I created a SCIM 2.0 OAuth Bearer Token template, I see only the option to pass token and the base url. But the problem is my token is only short lived, so it expires after a certain time.
What I would like is that okta should be able to hit one of my endpoint to fetch the token and then use it for user provisioning usecases.
I cannot see any option to pass authorization server url not the client id and client secret.
Is it possible to do so?