We should probably just move the admin account data (the parts that
are framework specific, ie the partyId and such should stay higher
level) to the common component or something.
In real life though, this is only useful for demonstration and
technically no "admin" account should ever exist, only accounts for
specific individuals. This is a good general practice and necessary
for things like PCI compliance.
-David
On Nov 19, 2008, at 12:37 PM, Adam Heath wrote:
We've been working toward a framework release. The framework contains
several webapps, all of which require you to log in. This is mostly
ok,
because the UserLogin table itself resides in framework.
However, there is only a single login available, system, which has no
password, and is disabled. So no one can access any of the deployed
webapps in base.
ps: setting the password and enabling the system account does work, so
it's probably just a matter of creating a new account just for this
purpose.
pps: unless of course we don't want the framework webapps to be
accessible until the applications are installed.
