Hi All, While analyzing the code of the UserAdmin implementation, Angelo and I found a interesting issue. The problem in this case is that the UserAdmin service should create an initial user (i.e. 'Administrator') upon the very first time this service is started. This user is required for first boot, after that the Admin will probably change its password or create new users and delete this one. Now the service needs to know when to create this user. Currently this is done by storing a 'INITIALIZED' configuration in ConfigAdmin,, sets it to true and the next time it starts it will skip creation of the admin user since this property is 'true'. In general, how should we cope with this? Setting this INITIALIZED configuration property in ConfigAdmin is not the proper way (it should be read-only), but how should this be implemented? Anyone any ideas?
Regards, Ivo and Angelo GX | Ivo Ladage-van Doorn | Product Architect | Wijchenseweg 111 | 6538 SW Nijmegen | The Netherlands | T +31(0)24 - 388 82 61 | F +31(0)24 - 388 86 21 | ivo.ladage-vandoorn at gxsoftware.com<mailto:ivo.ladage-vandoorn at gxsoftware.com> | www.gxsoftware.com<http://www.gxsoftware.com> | twitter.com/GXSoftware<http://twitter.com/GXSoftware> -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.amdatu.org/pipermail/amdatu-developers/attachments/20101008/d40f5430/attachment-0001.html
