Thanks.
I am experimenting with
the last option. I am using Impersonation to change my identity at the start of
each test, and I am reading the login information from an XLS file. This is all
in a test environment, so I don’t have any security concerns about storing
username/passwords in the XLS file. After I am done, I hope to find the time to
create a sample to post back to the site.
Thanks for your help
and guidance.
Stan
From: Rockford
Lhotka [mailto:cslanet@lhotka.net]
Sent: Monday, March 24, 2008 11:00
AM
To: Stanley
Canepa
Subject: RE: [CSLA .NET]
Visual Studio Test of BO - Custom Identity
If you are using a
custom principal (which you are from your problem description), then you totally
control how that principal is established. If you create a DataPortal_Fetch() in
your identity object that can load from an XLS file or whatever, then you can do
that. Or if you have a separate DAL behind your identity object, then perhaps
you can use a provider model to load some other DAL implementation that reads
the XLS instead of your normal security database.
Or if you want to
use your normal security database, then perhaps you can have some code in your
test project that loads the XLS and provides the appropriate username/password
at the start of each test.
Those options come
to me off the top of my head anyway.
Rocky
--------------------------------------------------------------------------- This message is for the sole use of the intended recipients and may contain confidential information. If you are not an intended recipient, you are requested to notify the sender by reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure or distribution is prohibited. Unless expressly stated otherwise, the sender of this e-mail message does not intend to be legally bound by any obligations expressed in this message or in any attachment not signed by pen and ink in a paper-based format. While the sender has taken reasonable precautions to minimize the risk of viruses, we cannot warrant the absence of, or accept liability for, any such viruses in this message or any attachment. We reserve the right to monitor all E-mail communications. ==============================================================================
--------------------------------------------------------------------------- This message is for the sole use of the intended recipients and may contain confidential information. If you are not an intended recipient, you are requested to notify the sender by reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure or distribution is prohibited. Unless expressly stated otherwise, the sender of this e-mail message does not intend to be legally bound by any obligations expressed in this message or in any attachment not signed by pen and ink in a paper-based format. While the sender has taken reasonable precautions to minimize the risk of viruses, we cannot warrant the absence of, or accept liability for, any such viruses in this message or any attachment. We reserve the right to monitor all E-mail communications. ==============================================================================
Copyright (c) Marimer LLC