-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Some comments inline;
>> >> 0) More on user provisioning: >> >> a. On startup, several accounts are created: >> >> i. System. The system account is the “author” of the built-in >> foundational services. The system account is of type Guest but for >> security reasons no logins under System should be allowed. While an >> Administrator can delete any of the foundational services, he should >> not be allowed to delete the System account. >> >> ii. WSO2 Mashup Samples. The samples account is the “author” of the >> built-in foundational services. The system account is of type Guest >> but for security reasons no logins under Samples should be allowed. An >> Administrator can delete any of the sample services as well as the >> Samples account. >> >> iii. Administrator. A default Administrator account with admin/admin >> should be provided for the user, although ideally on install or first >> run we’d allow the user to replace this account with his own (e.g. I’d >> like mine to be jonathan and select my own password). >> > The 'system' and 'samples' accounts and resources can be created in the > registry and privileges assigned to resources within these directories. > The admin account currently gets a directory in the registry with > authority being granted to the 'admin' user, so we can create an admin > level account with a name specified by the user in a similar manner. > However we may require a system account with full privileges, that is > guaranteed to retain the id/password, in order to create instances of > the secure registry, for example. > One thing I noticed is that for the Admin user, the appropriate roles are not assigned at present in user manager. the current admin/admin account has the role 'everyone' I discovered this during Task Panel filtering, where certain links are available only for the Admin role. >> > The deployer's polling mechanism would initially be one way; it will > identify new scripts on disk, not missing ones that exist in the > registry, so restoration would not happen. >> I noticed this when I implemented the service deletion functionality. Can't we update the registry when undeploying a service? I have similar code in the undeployment section, which stops the scheduler allocated to a service getting deleted. Tyrell - -- Tyrell Perera Senior Software Engineer; WSO2, Inc.; http://www.wso2.com/ email: [EMAIL PROTECTED]; cell: +94 77 302 2505 "Oxygenating the Web Service Platform." -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHWi3UehFdPcgGx7oRAmneAJ9odTheZvFDtMfXx11sQ9cEWOjsaQCg2LPV HHcl0obi5VQU4w5y488g9xw= =yFkI -----END PGP SIGNATURE----- _______________________________________________ Mashup-dev mailing list [email protected] http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
