Deployment:Deploying Firefox: Difference between revisions

Line 549: Line 549:




== sample:  scratch design: 'Corporate Firefox' Toolkit  ==   
== design sketch: 'Corporate Firefox' Toolkit  ==   


=== possible design of a toolkit for firefox customization, deployment and management on a corporate network ===   
=== possible design of a toolkit for firefox customization, deployment and management on a corporate network ===   
Line 562: Line 562:




The primary demand defined as always:
The primary demand defined as conditio sine qqua non:
  The product can be installed, managed and used
  The product can be installed, managed and used
with only minor changes neccessary to be expected  on the existing it infrastructure.  
with only minor changes neccessary to be expected  on the existing it infrastructure.  




Such a product might consist of:
Such a product could consist of eg.:
   
   
- corporate manager tookit:  
- corporate firefox manager tookit:  
- run as ff addon or xul app
- run as ff addon or xul app
- plugin interface and structure, plugins  are addons
- plugin interface and structure, plugins  are addons
Line 575: Line 575:




provide functions and categories required for management of the main package and as framwork for additional payload addons via network :  
provide functions and and interfaces:
- required for lifecycle management of the main package, compliant with ITIL
- to act as framework for other addons  
 
Possible category structure for modules:  
- configuration and settings:   
- configuration and settings:   
- policy - apply configuration settings to firefox installations assigned to groups, define and distribute mandatory settings, lockdown of user - read/write access to all or parts of the configuration     
- policy - apply configuration settings to firefox installations assigned to groups, define and distribute mandatory settings, lockdown of user - read/write access to all or parts of the configuration     
Line 590: Line 594:




possible modules:
possible structure and functions of a manager application:
 
- corporate firefox manager:
- corporate firefox manager:


Line 608: Line 613:




=== Required: 
interface definition for unified functions every module and ff-extension shoudl support to allow:
- unified acls defining access to addon function groups or single items (eg. user may run some addon - function, and can see but is not allowed to make changes, eg. a the lue of a backup-path.
possible approach: labeling of functions or gui elements/functions with security permissions and/or unique identifier (something like a sec-guid) as pointer to permission definitions stored in a sqlite database (what is official mozdev approach?   


- support for global security and configuration policys


=== scratch design:  possible corporate user-level applications using the tookit as management framework ===
=== design sketch:  possible corporate user-level applications using the tookit as management framework ===


=== functions and features possibly usefull in corporate networks ===  
=== functions and features possibly usefull in corporate networks ===  
61

edits