Generate an okta oidc token or a google auth oidc token within a workflow to outside API
I am trying to either use OKTA to geneartate an OKTA oidc or connect to google and get Auth OIDC token. I have no idea where to start. Does anyone have any clues or suggestoins
Former User
Posted 5 years ago · Edited 2 years ago·Last reply 5 years ago
5 comments
Former User
OP5 years ago · EditedYes that is what we figured why it wasn’t recommended because Collibra doesn’t listen for a response. So we are ok with that. We really just want to connect and make a call to an API to kick off a process once a table asset gets to accepted status
Former User
OP5 years ago · EditedI do have a coaching session scheduled and I do understand that it’s not recommended however we still want to pursue this because it will work better for our use case.
Can you tell me if it is possible to do what i am asking
Former User
OP5 years ago · EditedI do have a coaching session scheduled and I do understand that it’s not recommended however we still want to pursue this because it will work better for our use case.
Can you tell me if it is possible to do what i am asking
pmahend3
·5 years ago · EditedHi Stephen,
It is possible to make 1-way outbound REST calls from workflow scripts but this will have to be an asynchronous fire and forget call. I haven’t been successful in making a call where I was able to receive a response from the called service.
Thanks
pmahend3
·5 years ago · EditedHi Stephen,
I’m not entirely clear on what your use case is but it’s not recommended to make external API calls using Collibra workflow scripts.
If your workflow needs to interact with external systems, you may want to build an external app (python, java, bash, MuleESB) that processes/messages data outside of the DGC and then uses the REST API to then push the required payload to the DGC workflow. I hope this helps but if possible, I would set up a session with a Collibra coach who can help guide you with this.
Cheers