TM1 Forum

Hello,
Is there a way to prevent users from accessing the cubes ?
I am in the middle of making changes to the TI processes and re-loading etc. I want to stop users from logging in. How can I do that?

telula wrote:Hello,
Is there a way to prevent users from accessing the cubes ?
I am in the middle of making changes to the TI processes and re-loading etc. I want to stop users from logging in. How can I do that?

Quick and dirty approach:
- Do a data save.
- Take a copy of the }ClientProperties.cub file in case anything goes wrong.
- Make sure that logging is on on that cube.
- Open a browse of the cube.
- Copy your password value into everyone else's Password cell.
- When you're done, open the log file viewer, find the transactions where you changed their passwords to yours, then roll them back.
- If anything goes wrong in that process, shut down the server, copy the }ClientProperties.cub file that you took a copy of on step 2 into the data directory and restart.

Or you could just send an e-mail to them asking them not to log in while you're making the changes...

Hi

I really like Alan's solution but unfortunately it doesn't quite work with Integrated Login being turned on.
Just in case you are using it, you would need to delete the values the UniqueID field instead(and bring them back after you are done).

Cheers

If you have no development server then Alan's suggestion is a pretty good hack to prevent users accessing the system. (If the UI is tm1 web only then you could also simply stop IIS.)

Really you should be making these changes in a test or development environment and then migrating the objects to production! If your organization hasn't shelled out for a development environment then you can still do development on your local server (the poor man's dev environment) and make sure whatever you are doing is tested and works before migrating to production. This is much more preferable to the alternative you are considering.

I did something similar recently via rules, forcing a password over most users - because of the encryption they couldn't use it. Take away the rule and the stored pwds came back.
Don't think you could interfere with integrated login without downing the server and changing type back to 1.

Hi David,

You are right, you cannot change the setting for IL without a restart. But without a UniqueID users cannot log on nevertheless.
Cheers