Hello, I've setup FIM and have been trying to treat it like a sharepoint application and federate it. My setup looks like this: My ADFS server is called adfs.domain.local FIM server is called fim.domain.local Right now, I have the baseline sharepoint site and federation working correctly. ie, goto https://fim.domain.local. It prompts for credentials from an external AD, login and success. However when I goto the extended application https://fim.domain.local/IdentityManagement/ >> it will prompt for ADFS credentials from adfs.domain.local >> then it will login. I will get a different error depending on what I've setup for my appl pool. ie. Network Service. One error I get is, no matter who I login as, It will log into FIM as the user configured for the application pool. The other error is Service not avaliable. Does anyone know why this would be happening? Thank you Dennis

AFAIK FIM Portal does not support the use of claims-based identities using SAML tokens for authentication. You need a Windows token. IMO Using Federation with the FIM Portal has no use because FIM requires an AD account for a user to be able to logon to the FIM Portal. A federated user from e.g. a partner is thus not able to logon to the FIM Portal because he has no AD account. Grtz, Eddie

This might be interesting reading for you: http://blogs.technet.com/b/identityjunkie/archive/2011/05/19/federating-fim-2010-using-uag-adfs-and-kcd.aspxDavid Lundell, Get your copy of FIM Best Practices Volume 1 http://blog.ilmbestpractices.com/2010/08/book-is-here-fim-best-practices-volume.html