Invoking masking job fails when VDB is created from dSource due to credentials

  • 0
  • 1
  • Problem
  • Updated 10 months ago
  • Solved

Our goal is to create automated masked VDBs from dSource. The steps followed are:

- VDB is created from dSource

- Masking rules are built in masking engine, executed and verified with VDB created above (enabled multitenant)

- Mapped these rules to dSource

- Spin off new VDB from dSource, but not able to invoke the masking job and getting error like "Make sure the Delphix Masking Engine instance is online and available"

- However, VDB is created, but log shows that MASKING_FETCH job for "unknown" completed successfully

- When I verified actual data, none of the fields are masked.

The root cause I can think of is, credentials entered to make connection in masking engine. We have an internal process, which generates random user and password on a daily basis and these credentials are used for connection.

However, I am not sure how these credentials are referred by Delphix when masking job is invoked during VDB creation. Anyone come across these kind of problem or any resolution you have?


Thanks,

Santosh


Photo of santosh kumar

santosh kumar

  • 350 Points 250 badge 2x thumb

Posted 10 months ago

  • 0
  • 1
Photo of Gianpiero Piccolo

Gianpiero Piccolo

  • 1,314 Points 1k badge 2x thumb
Hi Santosh,

this article can help you:
https://support.delphix.com/Delphix_Masking_Engine/Masking_Engine/How_to_change_the_port_number_on_t...

This article is intended to help to change the TCP Port, but this show you how to configure all connection parameters to the masking engine from the virtualization engine, included the credentials (password).

Best regards.
Gianpiero
Photo of santosh kumar

santosh kumar

  • 350 Points 250 badge 2x thumb

thanks for sharing the info.

By looking command, changing TCP port will help if any issue with UI  access with masking engine,  which is working fine in our case. In fact, communication is established between delphix server and masking engine as I am able to see the jobs.

Please let me know your view

Photo of Gianpiero Piccolo

Gianpiero Piccolo

  • 1,314 Points 1k badge 2x thumb
I misunderstood your message. I thought there was a mismatching between the credentials for accessing to the masking engine.
Unfortunately I can't help you on your case.
One question: did you assigned masking job to the source and then used it in the combo box in the provision wizard? This operation makes a temporary DB Connection when provision the VDB. This temporary connection uses the new connection string (for the new VDB you're provisioning) but leaves username and password unchanged from the original connection.
Best Regards.
Gianpiero
Photo of santosh kumar

santosh kumar

  • 350 Points 250 badge 2x thumb

Yes, I did the way you explained. This is useful info that you highlighted above. Let's take an example:

user (SS)/password (Test123)/SID (PCP123)

These user & passwords are generated from Vault software when PCP123 SID instance is registered and same details are entered while adding connection in masking engine

Let's say engine is trying to create new VDB called XVZ234 with masking rules mapped, having same user ID & Password doesn't work as XYZ234 is not registered yet with Vault software where it generates random user ID & Password.

Is there any log file to check what is happening while invoking masking job during VDB creation? It is stopping us to progress creating masked VDBs. Thoughts are welcome !!