MaximumLoginAttempts parameter not working

[luqasshh]

Hello,
I have a problem with maximumLoginAttempts parameter in tm1s.cfg file of TM1 server in our Cognos Express installation. It is not working. Whatever the value I set it to, the number of attempts is not limited, like it's set to infinity or isn't set at all. I tried:
-restarting the TM1 server Windows service,
-restarting the TM1 admin server service,
-restarting Cognos Express Windows service,
-try to log in as an administrator or non-admin user

I have IntegratedSecurityMode parameter set to 5

I tried googling it, no result, neither in ibm documentation regarding tm1s.cfg parameters.

Any suggestions appreciated.

Regards,
Lukasz

[MFGF]

Hello,
I have a problem with maximumLoginAttempts parameter in tm1s.cfg file of TM1 server in our Cognos Express installation. It is not working. Whatever the value I set it to, the number of attempts is not limited, like it's set to infinity or isn't set at all. I tried:
-restarting the TM1 server Windows service,
-restarting the TM1 admin server service,
-restarting Cognos Express Windows service,
-try to log in as an administrator or non-admin user

I have IntegratedSecurityMode parameter set to 5

I tried googling it, no result, neither in ibm documentation regarding tm1s.cfg parameters.

Any suggestions appreciated.

Regards,
Lukasz

Hi,

If I'm remembering correctly, that parameter in tm1s.cfg is (was) explicitly for TM1 native security - not for the embedded Express authentication provider or Active Directory (which Express can also be configured to use). With IntegratedSecurityMode set to 5, the TM1 instance looks to the authentication provider set up within the BI architecture, so any native TM1 security parameters don't apply.

Cheers!

MF.

[luqasshh]

Thank you for your response.
In  that case this parameter should work if I set IntegratedSecurityMode to 1, right? Still, even if it's set to 1 MaximumLoginAttempts doesn't work. Any suggestions?

UPDATE: sorry, my mistake - I didn't restart the service last time. Now I get the old-style TM1 login window and my MaximumLoginAttempts parameter works. Also, now I can't log in as a Cognos user. That's okay, because I read that integratedsecuritymode set to 1 searches only for users that are in TM1 database. The question is - is it the Cognos Express limitation that I can't create any new user via TM1 with this security mode? When I try to do so I get a Cognos Express window where i can choose users or groups from Cognos, but there's no way to create a new user
Regards

[MFGF]

Thank you for your response.
In  that case this parameter should work if I set IntegratedSecurityMode to 1, right? Still, even if it's set to 1 MaximumLoginAttempts doesn't work. Any suggestions?

UPDATE: sorry, my mistake - I didn't restart the service last time. Now I get the old-style TM1 login window and my MaximumLoginAttempts parameter works. Also, now I can't log in as a Cognos user. That's okay, because I read that integratedsecuritymode set to 1 searches only for users that are in TM1 database. The question is - is it the Cognos Express limitation that I can't create any new user via TM1 with this security mode? When I try to do so I get a Cognos Express window where i can choose users or groups from Cognos, but there's no way to create a new user
Regards

If you are using IntegtratedSecurityMode 1, in theory you should be able to launch Architect, log in as a TM1 Administrator, then go to Server > Security > Clicnts/Groups. From here there should be able to select Clients > Add New Client to add a new TM1 user.

Cheers!

MF.