Hi,
I have installed TM1 server 10.1.1 on Windows 2008 RC2 (server computer). I have installed TM1 Architect on Windows XP (client computer). To login into TM1 I have set to use Cognos BI (version 10.2) as log-in mechanism (so CAM authentication). Web browser is connecting to web server using https connection. That is why certificate question exists. File tm1.cfg at TM1 server has two settings:
ServerCAMURI=http://<ip_address>:9300/p2pd/servlet/dispatch
ClientCAMURI=https://<ip_address>:443/ibmcognos/cgi-bin/cognos.cgi
1. Start TM1 Architect from client computer.
2. Click on plus at TM1 and <server name> is displayed.
3. Clicking on <server name> and Security Alert about invalid certificate is displayed:
The name on the security certificate is invalid or does not match the name of the site.
4. I have clicked on View Certificate and I see the certificate is CA signed certificate (it is not self signed certificate!)..
5. Clicking on Yes button it continues without any problem, Cognos BI login is displayed.
So everything is working fine, just this annoying info at every TM1 login.
There should probably be some settings, which one?
Architect login: The name of security certificate is invalid
-
- Posts: 133
- Joined: Thu Mar 25, 2010 8:34 am
- OLAP Product: Cognos TM1
- Version: 9.5.2
- Excel Version: 0
Architect login: The name of security certificate is invalid
- Attachments
-
- security_alert.png (9.68 KiB) Viewed 3497 times
- qml
- MVP
- Posts: 1096
- Joined: Mon Feb 01, 2010 1:01 pm
- OLAP Product: TM1 / Planning Analytics
- Version: 2.0.9 and all previous
- Excel Version: 2007 - 2016
- Location: London, UK, Europe
Re: Architect login: The name of security certificate is inv
Open an Internet Explorer window and go to Internet Options -> Content -> Certificates -> Untrusted Publishers. Find the appropriate security certificate and click Remove, then confirm.
Kamil Arendt
-
- Posts: 133
- Joined: Thu Mar 25, 2010 8:34 am
- OLAP Product: Cognos TM1
- Version: 9.5.2
- Excel Version: 0
Re: Architect login: The name of security certificate is inv
qml, I have tried your suggestion but when logging into TM1 it still reports the same problem. As I see in Untrusted Certificates there were two Verising certificates, but I am using StartCom certificates - so this is not the problem. It must be something else.