Setting TM1 Password Restrictions

[fleaster]

Hi all,
Just wondering if it's possible to set TM1 password restrictions, so that when a user sets a password it's compulsory to be:

1. a minimum length
2. must contain a combination of capital and lowercase letters
3. must contain a special character OR
4. must contain a number

...now I know #1 is possible via the PasswordMinimumLength parameter in the cfg file, but was not aware of any parms to do #2-4... anyone have any ideas?

Cheers,

Matt

[lotsaram]

You ca set the minimum length, number of login attempts and days until a password expires.
That's it. No special character checks, no complexity checks, no similarity to last password checks.

If you have any of these requirements then honestly the only solution I would consider is single sign on with the AD where all this is managed because that's its job.

Actually one thing I'm really looking forward to in Planning Analytics is the return of windows integrated login for all UIs so that I no longer have to deal with the steaming pile of abomination that is CAM.

[fleaster]

cool that's kind of what I expected anyway..

[harrytm1]

You ca set the minimum length, number of login attempts and days until a password expires.
That's it. No special character checks, no complexity checks, no similarity to last password checks.

If you have any of these requirements then honestly the only solution I would consider is single sign on with the AD where all this is managed because that's its job.

Actually one thing I'm really looking forward to in Planning Analytics is the return of windows integrated login for all UIs so that I no longer have to deal with the steaming pile of abomination that is CAM.

Hi lotsaram, I don't quite understand your point about return of Windows integrated login versus CAM. Are you referring to the use of control cube Client Properties where we can enter the Windows domain ID so that a user can simply double click a model in Perspectives and it will login without providing password?

As for AD, Planning Analytics will still need CAM which is installed through Cognos Analytics installer, correct? Or is there a new feature in PAL that I miss?

Look forward to your reply!

[declanr]

I assume Lotsa was referring to the fact that in 10.1 and earlier you could set up mode 2 or 3 to use SSO through NTLM or Kerberos.
In 10.2 that still worked for perspectives/architect but not the web clients.
In PA 2.0 IBM have reintroduced a way to get Kerberos SSO working for the web clients again.
I believe that PAW is 1 or 5 only though.

[lotsaram]

As for AD, Planning Analytics will still need CAM which is installed through Cognos Analytics installer, correct? Or is there a new feature in PAL that I miss?

I believe that PAW is 1 or 5 only though.

Yes that's true (for now) but I believe it is IBM's intention to bring in support for native AD SSO ASAP, and a good thing too!

PAW Local v2 currently supports Mode 1 & 5.
Efforts are underway to support the remaining Modes with 3 being a priority

[declanr]

That will be good; I am just happy its back for web which will be the bigger benefit to most customers over the next year or so anyway.