TM1 Forum

IBM Cognos TM1 10.2.2 with Cognos BI (Users security and cube data source) on IBM Aix
Ldap on Cognos BI security. (On TM1 server, IntegratedSecurityMode=5)

After the ssl problem, we suceed to configure the tm1 plateform using option 4 ( certificate version = 2 with tm1ca_v2.pem). All services OK.
http://www-01.ibm.com/support/docview.w ... wg21697266
But we still have a probleme with the Bi plateform. All services start, we can run a report, but it fails before the end.
Obviously, when we test the datasource (In cognos administration, it fails).

The only way I identify is with the tm1.sslconfigs.xml on the Bi plateform?

My question is :
Who choose option 4 with a TM1-BI plateform,and how do you suceed the configuration?
Does it need to use custom certificate?

Cordially:

I found someone else with this configuration, who applied the v2 certification method.
http://www.tm1forum.com/viewtopic.php?t=12728&start=60

Re: SSL breaks on Nov 24
Postby Steve Vincent » Fri Sep 23, 2016 12:10 pm
http://www-01.ibm.com/support/docview.w ... wg27041183
Step 3 of this technote covers what needs to be altered on a BI server using TM1 as a data source in order to swap it to the v2 cert. After a restart of the BI services this works fine, have tested it on the following;
TM1 10.2.2 FP1 IF1015
BI 10.2.1 FP4
Both on Windows Server 2012 64bit
Ensure that the full local path to the cert is entered into the xml file.
If this were a dictatorship, it would be a heck of a lot easier, just so long as I'm the dictator.

But we are on TM1 10.2 FP1
Is there anybody else to confirm it's OK on 10.2.2 FP1?
In this case, we will install all FP to 10.2.2

I never replied:
As read somewhere in this forum, TM1 10.2.0 have a bug with 2048 bit certificate , only in some parts, like pmhub and cafe.
If your BI and TM1 server is the same, it's OK. You just have to properly configure tm1.sslconfigs.xml file on your BI install and it work with v2 certificate (but no supported by IBM).
In the case BI and TM1 are on different server, you must use new ssl v1, or migrate to > TM1 10.2.2.4.