Page 1 of 1

Multiple-domain Login

Posted: Wed Jun 08, 2016 7:00 am
by wilsonmax
Does anyone here use multiple domain login? :mrgreen:
Is there any settings need to be done? :?:

According to an IBM reference, we've added the user (from another domain) in TM1 as <username>@<userdomain>.
However, when we tried to integrated login, it prompted message 'Log In Failed: SystemServerClientNotFound'. :(

tm1s.cfg
SecurityPackageName=Kerberos
IntegratedSecurityMode=2

Reference
http://www-01.ibm.com/support/docview.w ... wg21456988

Remarks
The connectivity of those domains should be OK, since other applications already supported users from both domain.

Re: Multiple-domain Login

Posted: Wed Jun 08, 2016 2:19 pm
by mattgoff
We use multi-domains successfully, so I can confirm it's possible. My advice would be to open a ticket with IBM on this one. Kerberos logging can be difficult to trace. I had an issue with Kerberos integrated login on TM1 Web and it took over a year and a dozen meetings w/ IBM before we finally found the right person to figure it out (bizarre issue, one of the files had been saved with the wrong encoding).

Matt

Re: Multiple-domain Login

Posted: Tue Jun 14, 2016 3:14 am
by wilsonmax
Thanks for your confirmation on the possibility.
I'll log a case to IBM.

Because from some IBM reference, most of them suggested 'Kerberos'. :ugeek:
Therefore, I used it.

May I know your TM1 version, and what kind of file encoded wrongly? :?:

Re: Multiple-domain Login

Posted: Tue Jun 14, 2016 2:51 pm
by mattgoff
wilsonmax wrote:May I know your TM1 version, and what kind of file encoded wrongly? :?:
Various revisions of 10.2. I don't recall the exact file, but it was one of the ones you have to edit to set up Kerberos integrated login for TM1 Web. Note that the failure mode of this issue was that integrated login on TM1 Web only didn't work at all for any domain. Integrated login via the client worked fine. I think my situation was probably different than yours-- my story was just to illustrate how tricky it can be to get it configured. Even with IBM's help it took a year resolve (granted I had it as a Sev 4 PMR so it wasn't at the top of anyone's priority queue, including my own).

Matt