Is there a way to set up the Reserve SMTP Agent for Secure SMTP?


For inbound SMTP messages to the TRIRIGA “ReserveSMTPAgent”, is there any way to configure it for Secure SMTP (SMTPS)? I know the port can change, but can the agent use the SMTPS protocol instead of SMTP, just by changing the port? You have clients using IBM TRIRIGA in the IBM Cloud and they cannot implement your Reservation Management product because of this major gap in the product.

The Reserve SMTP agent does not currently support encrypted TLS communication. Please create a request for enhancement (RFE) to request that capability be added to the Reserve SMTP Agent.

[Admin: To see other related posts, use the SMTP tag or TLS tag.]

Continue reading

How do you fix failure to export reports to Excel due to timeout?


There are many installation scenarios that can cause TRIRIGA reports, especially BIRT reports, to fail to export due to timeout. Microsoft Excel exports are often the ones that you can observe because all of the file formatting happens during export.

Let’s focus on WebSphere Liberty installations, but this recommendation can be used for other web servers with some tweaks. Mostly, this is related to timeout settings, especially for HTTPS (SSL/TLS) connections. A good troubleshooting test is to perform the same action in a non-HTTPS (HTTP) connection. Does the report export? If so, take note of the time needed to export it and plan to extend the timeout in the HTTPS connection to at least double the time.

Refer to the IBM Knowledge Center > WebSphere Liberty > HTTP Endpoint topic. Look for the “sslOptions”, and also double-check the “httpOptions”, for timeouts.

[Admin: This post is related to the 04.20.17 post about setting the TRIRIGA session expiration warning in the portal. To see other related posts, use the Timeout tag.]

Continue reading

IV95388: TRIRIGA Reserve Outlook add-in fails when using only TLS 1.2


Due to security regulations, certain customers must disable TLS protocols 1.0 and 1.1. However, when they do this and use only TLS 1.2, they lose connectivity from the TRIRIGA Reserve Outlook add-in.

The problem was that the add-in was compiled with .NET 4.0 which doesn’t support TLS 1.2. The fix is to explicitly force support for the TLS 1.2 protocol. Moving forward, the IBM TRIRIGA Workplace Reservation Manager add-in is now able to communicate with the TRIRIGA server over the TLS 1.2 protocol.

[Admin: To see other related posts, use the Add-in tag or TLS tag.]

Continue reading

How do you configure TRIRIGA to use TLS 1.1, TLS 1.2, or SSL?


Does TRIRIGA support TLS 1.1 or TLS 1.2 or SSL? If yes, what steps do I need to take to make TRIRIGA use one of these protocols?

TLS and SSL, from a TRIRIGA perspective, are supported by certificate technology for security and use HTTPS URLs. TRIRIGA works with HTTPS: Does IBM TRIRIGA support HTTPS, SSL and TLS? As a result, TRIRIGA can be used with TLS and SSL, regardless of the version.

There is no TLS or SSL configuration necessary within TRIRIGA. If TLS 1.1 or TLS 1.2 or SSL is properly configured through your application server and web server, TRIRIGA can be used with it. TLS and SSL are security configurations using certificate installs that exist outside of TRIRIGA. The TRIRIGA Support team cannot assist with environmental configurations of these technologies. Clients should work with their application server vendors (e.g., WebSphere, WebLogic) as well as other infrastructure-related technologies (e.g., web servers, load balancers, etc.) to properly configure these.

[Admin: This post is related to the 09.30.14 post about whether TRIRIGA supports HTTPS, SSL, and TLS, and the 04.10.17 technote about TLS, SSL, and HTTP.]

Continue reading

Does IBM TRIRIGA support HTTPS, SSL and TLS?


Are HTTPS, SSL and TLS supported by IBM TRIRIGA product? I need to implement HTTPS, SSL and TLS for my IBM TRIRIGA solution.

The Transport Layer Security (TLS) and its predecessor, Secure Sockets Layer (SSL), are both supported via Hypertext Transfer Protocol Secure (HTTPS). The HTTPS protocol is the result of simply layering the Hypertext Transfer Protocol (HTTP) on top of the SSL/TLS protocol, thus adding the security capabilities of SSL/TLS to standard HTTP communications. This is implemented via Web Server configuration. We have tested HTTPS for IBM TRIRIGA and support it via Web Server set up. See: Enable HTTPS in WebSphere for Maximo, SCCD, TSRM, and TRIRIGA.

But we do NOT support:

  • Secure Shell (SSH) on the IBM TRIRIGA system. But during installation, the IBM TRIRIGA installer may connect to the application server as the IBM TRIRIGA user via the SSH protocol. Another remote terminal application protocol may be used as well. See the IBM TRIRIGA Application Platform Version 3.4.1 Installation and Implementation Guide [PDF].
  • The Microsoft Remote Desktop Protocol (RDP) proprietary protocol.
  • The encrypting communication session IP packet Internet Protocol Security (IPsec) protocol suite. Your application server may support it, but this has never been tested by IBM TRIRIGA.
  • The Citrix Systems proprietary application server Independent Computing Architecture (ICA) protocol.

[Admin: This post is related to the 08.04.16 post about configuring TLS or SSL, and the 04.10.17 technote about TLS, SSL, and HTTP.]

Continue reading