I want to make Https call to Okta from a workflow. So to connect to Okta, like in the SaaS Okta connector, the preferred route is to use Private key to generate jwt token and use this jwt token to generate the access-token or the API token route. We cannot use clientID, clientSecret route(custom authorization server).
Pivate key route:
I dont think there is a way that we can use the private key to generate the jwt token and then use this in the Https call to get the access token
API Token route
Is it possible to use API token as auth in http call within workflow?