Updated on January 9, 2024

Step 3: Protecto Tokenization Deployment

Tokenization Service


Deploy Protecto tokenization services in Kubernetes:

sh tokenization.sh

This script will prompt you to enter various configuration values required for the deployment.

Configuration Values

Running the script will prompt for the following values:

  • DB Host (e.g., demo.example.com): tokenization.protecto.com
  • DB Username: Ao2BdCCv.root
  • DB Password: Ao2BdCCvD4OoSE
  • DB SSL Certificate Path: /etc/ssl/certs/ca-certificates.crt
  • Support Email: support@example.com
  • Support Email Password: ExamplePassword
  • Mail Server Host: smtp-mail.outlook.com
  • Mail Server Port: 587
  • Docker Email: support@example.com
  • Docker Username: example
  • Docker Password: ExamplePassword

Testing with IP (http)

After running the tokenization.sh script, the Protecto tokenization services will be deployed, and you can start testing with the following endpoints:

Nginx Config (Optional)

If you intend to expose Protecto publicly and want to set up domain mapping using Nginx, follow these steps to deploy the Nginx Ingress Controller in Kubernetes.

sh azure_nginx.sh

Testing with Domain (https)

After running the tokenization.sh file and completing the Nginx Ingress Controller deployment, you are ready to use Protecto tokenization services with the following endpoints:

Additional Information

For more detailed information on Protecto Tokenization APIs and usage, refer to the Tokenization APIs – Protecto documentation.

If you encounter any issues or have questions, please contact our support team at support@example.com.

What are your feelings?
Scroll to Top