Authentication/authorization should be a separate concern. I agree with Felix, WebConsole was never designed as an end-user tool, it is technical in nature and will allow end-users to screw things up in many interesting ways.
What you need is a layer on top of Configuration Admin that will take into account users and their roles and show/hide/make read-only configuration data based on that. Greetings, Marcel On Jun 25, 2013, at 12:43 PM, Felix Meschberger <[email protected]> wrote: > Hi Hugh > > The Web Console Configuration Manager tab allows for changing all > configuration stored in the Configuration Admin service and/or described by > the Metatype Service. Hence existing configuration is always displayed even > if not described. > > There is also currently no such thing as read-only configuration. Because at > then end of the day: everything can be stored in a Configuration object and > the Configuration Admin service does not care about it (as long as the data > types of the configuration are supported). > > Now, the Web Console is not destined at regular passers-by users but at > system administrators which can be expected to be knowledgable. So I don't > this is such a huge problem -- but that's me ;-) > > To your question: While you cannot hide the configurations as of today, there > would be a number of options: > > (a) define an empty descriptor file for the factory PID. This will then just > show empty forms for the configuration. Such configurations can still be > "unbound" or removed. > > (b) we add a Web Console configuration option to select whether to show or > hide existing configurations for which no Metatype descriptor exists (such an > option does not exist yet and would be an extension) > > Regards > Felix > > Am 25.06.2013 um 00:27 schrieb Rodgers, Hugh: > >> Hello - >> >> We have Managed Service Factories (MSFs) that we programmatically create and >> configure at runtime. We do not want these MSFs to be displayed on the Felix >> Web console's Configurations tab to prevent user from attempting to modify >> these MSFs. We had achieved this by not specifying a >> OGSI-INF/metatype/metatype.xml file for these MSFs, but with our recent >> upgrade of Felix these MSFs are now displayed on the Configuration tab. >> (possibly due to FELIX-3227 ticket's fix). >> >> How can we suppress these MSFs from being displayed on the Configuration >> tab? If this is no longer possible, is there a way to make all of the fields >> in the metatype.xml be non-editable? >> >> Thanks - >> >> Hugh >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
