I was testing Operation Console few months back with TM1 10.2.1 using CAM SSO (with AD) and even though there are some bug in the login validation javascript. I managed to get the integration works.
However, just move to 10.2.2 and there is a change in the login box to Operation Console for specifying the Namspace ID. It actual breaks the setup and I can no longer login using the CAM SSO approach. Normal TM1 authentication mode still work though.
I cam pretty sure the Namespace ID specify is correct as under CAFE, it uses the same login box in which you will need to specify the namespace ID and I am able to to login CAFE using the CAM SSO.
Anyone out that have the same setup and managed to get this working ? Pretty annoying problems with Ops Console, staying put with TM1Top from older version which still works well.
10.2.2 Operation Console changes break CAM SSO
-
Steve Vincent
- Site Admin
- Posts: 1054
- Joined: Mon May 12, 2008 8:33 am
- OLAP Product: TM1
- Version: 10.2.2 FP1
- Excel Version: 2010
- Location: UK
Re: 10.2.2 Operation Console changes break CAM SSO
Probably related to a regression bug with SSO...
http://www-01.ibm.com/support/docview.w ... wg1PI22572
I'm still awaiting a hotfix for it as it renders TM1 data sources useless with BI.
http://www-01.ibm.com/support/docview.w ... wg1PI22572
I'm still awaiting a hotfix for it as it renders TM1 data sources useless with BI.
If this were a dictatorship, it would be a heck of a lot easier, just so long as I'm the dictator.
Production: Planning Analytics 64 bit 2.0.5, Windows 2016 Server. Excel 2016, IE11 for t'internet
Production: Planning Analytics 64 bit 2.0.5, Windows 2016 Server. Excel 2016, IE11 for t'internet
-
kangkc
- Community Contributor
- Posts: 206
- Joined: Fri Oct 17, 2008 2:40 am
- OLAP Product: TM1, PA , TMVGate
- Version: 2.x
- Excel Version: 36x
- Location: Singapore
- Contact:
Re: 10.2.2 Operation Console changes break CAM SSO
Thanks. I don't think this is the issue.
After trying for 2 days, I managed to get it working partially and this is what I have done:
1. Use /pmhub/pm/admin to point to the sample instance SData. Admin host must be localhost (still trying to figure out why) else it won't work, also set SingleSignon to true
2. Once the above is configured, you can proceed to /pmhub/pm/opsconsole
3. In Operation console, add both the sample instance as well as the TM1 instance that is using CAM SSO
4. Once the TM1 instance is added, you can now kill thread, Operation Console will prompt for the ID and password for the first time, which is in the format Namespace ID\Username
However, I couldn't get the message log, transaction log working for this instance whereas I have no problem getting the log for the sample instance.
After trying for 2 days, I managed to get it working partially and this is what I have done:
1. Use /pmhub/pm/admin to point to the sample instance SData. Admin host must be localhost (still trying to figure out why) else it won't work, also set SingleSignon to true
2. Once the above is configured, you can proceed to /pmhub/pm/opsconsole
3. In Operation console, add both the sample instance as well as the TM1 instance that is using CAM SSO
4. Once the TM1 instance is added, you can now kill thread, Operation Console will prompt for the ID and password for the first time, which is in the format Namespace ID\Username
However, I couldn't get the message log, transaction log working for this instance whereas I have no problem getting the log for the sample instance.