IdStory Identity Manager

I see 2 different issues in this ticket

1) Install guide that exist also as installation checklist. Plese Petr Fišer, can you merge these two docs. The aim is that there is only one install guide/checklist available (even as downloadable .doc). Otherwise we will sooner or later come across the same situation that one of the document is not up to date.

2) Be able to easily see that IdM is using non persistent DB. It this I agree with Petr Michal. Everyone can make a mistake in configuration and now it is not obvious, that I do not run proper DB. Flag similar to "test" in GUI would really help.

To prevent this, checklist should also have something like basic checks - 7 to 10 points to check after the installation is done like: * server reboot after which idm is running and has all data, * server is running proper DB (create and delete user and check in DB?)...

Development / Test environment label is shown on FE (it's loaded from property file + profile).

I think we have more than one configuration, which can be potentially dangerous (h2, default crypt key, default attachment storage ...) as Ondra says. So some universal mechanism for dangerous configuration item will be created (and it's needed to implement alert closing - i don't want to see this alerts on demo installations all time etc.).

I don't need an alert panel in the middle of the screen saying "Warning! You're running on H2 repository! Everything you do will be lost after restart!", I just need some way to determine in GUI whether is the IdM using H2 or a persisted DB. Might be just some kind of "info" property in profiles using H2 or something like that.

All configured properties can be found in confinguration (System -> Configuration).

Is there any property saying that the application is using H2 or is not using PostgreSQL? If not please add such property to all the default profiles using H2. Thanks.

I think we have more than one configuration, which can be potentially dangerous (h2, default crypt key, default attachment storage ...) as Ondra says. So some universal mechanism for dangerous configuration item will be created (and it's needed to implement alert closing - i don't want to see this alerts on demo installations all time etc.).

But I'm not looking for an universal mechanism to warn admin that a potentially dangerous configuration is loaded. And as I said previously, no popping alert message is requested. I just want to know - as the title says - in GUI (might be in configurations) whether is the application running on the H2 DB or on PostgreSQL, nothing more, nothing less.

We could add this in a similar way the "Development" label is added to the right upper corner of the GUI when running under dev profile. This is unobtrusive and visible at the same time.