Configuring the Token Proxy Exchange Service

To configure the Token Proxy Exchange Service follow these guidelines:
  • To manage the Token Proxy Exchange Service use the web portal and create a system administrator account. Enter the user name as the employee’s email, then an email is sent to the system administrator account that contains a link with a unique password reset token. Choose a new password by meeting the password requirements.

  • After you create the system administrator account, you can create the other users and clients. Use the client user accounts to configure the third-party payment service provider connections. Define the user name and password for basic HTTP authentication in OPERA.

  • You must change the password frequently following the guidelines for:
    • database user

    • web portal user

    • HTTP authentication

  • The PSP Client Side Certificates expiration date depends on what the PSP is set during creation of the certificate. Check the expiration date in the properties of the certificate files. Be aware the PSP certificates must be updated prior to the expiration date to avoid downtime to the interface.

Replace the default self-signed certificates with CA signed

When Tomcat is selected as web server to host TPS web portal, the installer will create a self-signed certificate for Tomcat as server’s certificate. In production, CA signed certificate is highly recommended. Please refer to the Oracle® Hospitality Self-Hosted Token Proxy Service Installation and Configuration Guide about “Tomcat – Certificate Configuration Wizard” and “Tomcat HTTPS Listener” for steps to replace self-signed certificate with the CA signed certificate.