AFDS, Domain trust or other?

Hello all,

I'm falling in a strange question. I've an exchange systems in my
domain. Using this exchange system I give a service to my customers
outsourcing the exchange.

Now, I've to sell this service to another customer. This customers do
not want for privacy/security/other reasons to trust its own domain with
my one but want to use for every user in its domain the local credential
to logon to my exchange service thought outlook and thought owa.

If I can use trust googling around I've found AD Federation services,
but seems to be that this systems works only for web applications. This
can be good for OWA but is unusable for Outlook client.

There's another trick to solve this?


Thanks
Stefano

Joe
Fri May 02 09:06:39 PDT 2008

ADFS won't help with Outlook here, sorry. You are correct in your
understanding that this is just for web applications in its current state.

I don't have another trick for you. I think you either need a trust or
would need to have shadow accounts for their users with matching passwords
provisioned in your forest (which is quite a bit more work and more
intrusive than doing the trust).

Joe K.

--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
--
"Ste" <s.c@i.net.it> wrote in message
news:680oeiF2ra4c5U1@mid.individual.net...
> Hello all,
>
> I'm falling in a strange question. I've an exchange systems in my domain.
> Using this exchange system I give a service to my customers outsourcing
> the exchange.
>
> Now, I've to sell this service to another customer. This customers do not
> want for privacy/security/other reasons to trust its own domain with my
> one but want to use for every user in its domain the local credential to
> logon to my exchange service thought outlook and thought owa.
>
> If I can use trust googling around I've found AD Federation services, but
> seems to be that this systems works only for web applications. This can be
> good for OWA but is unusable for Outlook client.
>
> There's another trick to solve this?
>
>
> Thanks
> Stefano