Does IBM TRIRIGA support HTTPS, SSL and TLS?

Question

Are HTTPS, SSL and TLS supported by IBM TRIRIGA product?

Cause

Need to implement HTTPS, SSL and TLS for my IBM TRIRIGA solution.

Answer

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 IBM TRIRIGA system, but see that during installation the IBM TRIRIGA installer may connect to application server as the IBM TRIRIGA user via SSH protocol (other remote terminal application protocol may be used as well, see IBM TRIRIGA Application Platform Version 3 Release 4.1 Installation and Implementation Guide );

- 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 out by IBM TRIRIGA);

- The Citrix System proprietary application server Independent Computing Architecture (ICA) protocol.

http://www-01.ibm.com/support/docview.wss?uid=swg21685881&myns=swgtiv&mynp=OCSSHEB3&mync=R

Workflow Modify Task blocked by Recent WebSphere Change

There was a recent change to WebSphere that may cause the a failure when editing a map in a modify task with a BO that has many fields.

To resolve the issue, login to the WAS Admin console:

In the left pane click > Servers > Server types > WebSphere Application Servers

In the right pane click server1

Click Web Container Settings->Web container->Custom properties



​Add a new custom property:

com.ibm.ws.webcontainer.maxParamPerRequest

set the value to

20000



Click Apply, click OK

Click Save

Taken from https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20TRIRIGA1/page/Workflow%20Modify%20Task%20blocked%20by%20Recent%20WebSphere%20Change

WebSphere and SAML

Thought this would be useful information if you are looking into SAML.

http://bastide.org/2014/03/04/saml-experiences-part-1/

TRIRIGAWEB.properties Front End Server Property

One of the most important properties that is easily overlooked is the Front End Server property. This property must be set for BIRT reports to render correctly on the application server. If you have a process server, the URL value of the Front End Server property on the application server and the process server must be the application server. It is also important to set this property for queued reports, since the generated URL is composed from this property. You can set this property during the installation process or in the TRIRIGAWEB.properties file, which requires a restart before it takes effect. The following example shows the property and its description from a 3.4.1 installation

#

# The FRONT_END_SERVER is the main URL an end user would enter to access

# the IBM TRIRIGA system. It consists of a protocol(optional),

# host[REQUIRED] and port (optional). If no protocol is specified

# then "http" will be used by default.

#

# Exampes:

# tririga.company.com

# tri-dev.company.com:8001

# https://tri-secure.company.com

# https://tri-dev-secure.company.com:8443

#

FRONT_END_SERVER=http\://hostname\:8001  

Taken from https://www.ibm.com/developerworks/community/blogs/9e3a5b9d-6a06-4796-a6c1-5137b626e39c/entry/front_end_server?lang=en