Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
Derek2
Contributor II
Contributor II

Password Vault Integration

Set up CyberArk to integrate with Talend using the guide https://www.talend.com/blog/2018/06/29/build-an-enterprise-level-password-vault-with-talend-and-cybe.... It is working and able to retrieve passwords. What I want to setup now is a joblet or job that can be used in with every job. When I tried to do this it was not passing the context values between the joblet or job and my other job. Has anyone used a password vault and integrated it into all of their jobs? What was your approach?

Labels (4)
5 Replies
Anonymous
Not applicable

Hello,

Could you please let us know if this article helps?

https://community.talend.com/s/article/Implementing-password-vaults-lNsRG

Best regards

Sabrina

Derek2
Contributor II
Contributor II
Author

I used the link for CyberArk from the article you shared and was able to test out the process. However it doesn't describe how to apply that to every job and I don't want to have to put the code in every job.

I think this link https://help.talend.com/reader/wT42luidfFi_RutoGODc6w/EzaSvCRGprcM69SBP8CAPg would show me what I need but it links to a page not found error.

Anonymous
Not applicable

Hello,

Please check the article here: How to set up encryption of the passwords in Talend Studio

Best regards

Sabrina

Derek2
Contributor II
Contributor II
Author

It appears then that the best approach is to write a custom routine that calls CyberArk and use that routine in my jobs. Is my understanding correct?

Alaor_Silva
Contributor
Contributor

@Derek Sutliff​,

 

I use the CyberArk just the way you proposed to use,

 

From the JobLet, I just used a tLoadContext to fill my context information,

 

As the JobLet and your main job share the same code, it should not be a problem

But if you ask me, what would be the best approach, I say Create a custom routine, it'll be easier for you to implement in all your Jobs just a routine call is better than a JobLet