Sign in
Microsoft.com
 
Microsoft
 
 
 
Microsoft >
> 
> 
> 
CRM 2011: IFD - Outlook 2010 Client not authenticating custom ASPX page

Proposed Answer CRM 2011: IFD - Outlook 2010 Client not authenticating custom ASPX page

  • Friday, May 20, 2011 2:03 PM
     
     
    Sign In to Vote
    0

    We have setup an internet facing deployment of CRM 2011 with Rollup 1 (server, email router, SRS data connector) and SQL Server on a separate physical machine. It is running great in the web browser but some of our custom ASPX pages are failing to authenticate in the Outlook client even though they work as intended in Internet Explorer.

    Some of our CRM 2011 custom ASPX pages were developed for CRM 4.0 and are deployed using the ISV folder. Our more recent pages have been deployed on a separate web site on the same physical machine as CRM configured for ADFS and single sign-on.

    We are having the following issues in the Outlook 2010 client:

    1. Any pop-up window that opens a new web browser (not an Outlook pop-up) will fail to persist the Outlook session/credentials so the ADFS login page is displayed (regardless if it is our legacy code or not).

    2. Our ADFS enabled code on the separate web site also shows the ADFS login page when displayed in an IFRAME on the Outlook client however the legacy CRM 4.0 code is working fine.


    If we could atleast get item number 2 working for our new code then we could also implement work arounds to use IFRAMEs instead of web browser pop-ups.

    I was wondering if anyone else in the community has faced these problems and managed to their custom code working in the Outlook 2010 client with an internet facing deployment of CRM 2011.

    Any other suggestions or tips would be greatly appreciated.

    Thank you

    Mike

     

All Replies

  • Wednesday, October 12, 2011 10:53 AM
     
     
    Sign In to Vote
    0

    Hi Mike,

    I'm having the same problem... Did you have any luck resolving this problem? 

     

    Kind Regards,

    Frederic

     
  • Wednesday, October 12, 2011 3:40 PM
     
     
    Sign In to Vote
    0

    No we haven't resolved this yet. As it turns out our client had to move away from the outlook client for IT reasons so we have been able to get by using the web interface. They are trying to get the outlook client approved by their IT department so we may have to work on this issue again if the approval comes through.

    Our client does use Active Directory on their premises so we may look at trying to get a single sign-on solution working with ADFS and a trust between the domains/servers but that still won't help us with other clients wanting to use the outlook client.

     
  • Thursday, October 13, 2011 8:12 AM
     
     
    Sign In to Vote
    0

    Hi,

    The only solution we can give our clients for now, is to open a browser and leave it open in the background.  In the browser you connect to your organization and you login to the CRM.

    If they do so, they're able to work through the outlook client without having to login each time. But this is a dirty workaround... I'm looking for a way to be able to impersonate the page, so that we are able to make it work without the dirty workaround.

     

    Kind Regards,

    Frederic

     
  • Friday, January 13, 2012 1:23 PM
     
     Proposed Answer
    Sign In to Vote
    0

    Hello,

    I'm having the same problem. Now after 3 months, have anyone resolved this problem?

     
  • Friday, January 27, 2012 4:19 AM
     
     
    Sign In to Vote
    0

    I dont remember which KB breaks it, but the problem is when you run windows update. It installs a Outlook KB that breaks the authentication. I had to uninstall all KBs then work my way back up.

     

    FYI - I did a fresh install of windows 7 and Office 2010 SP3 with no updates and it works without any issues

    MCSE, MCDBA, MBSCM
     
  • Wednesday, February 29, 2012 2:54 PM
     
     
    Sign In to Vote
    0

    Did anyone verify the KB that breaks this as we are experiencing a very similar problem :(

     
  • Thursday, March 01, 2012 4:39 AM
     
     Proposed Answer
    Sign In to Vote
    0
    We faced a very similar issue with custom ASPX pages created for us by a vendor not working with IFD.  After fighting it for a while, we finally delayed implementing IFD, and then re-wrote all of the ASPX pages as HTML/Javascript web resources.  Once we did that, implementing IFD was a breeze.  From what I can tell, Microsoft recommends using client side HTML/Javascript over ASPX pages in CRM.

    Berel Lax


    • Edited by berel_lax Thursday, March 01, 2012 4:56 AM
    • Proposed As Answer by berel_lax Thursday, March 01, 2012 4:56 AM
    •  
     
  • Tuesday, June 19, 2012 1:21 AM
     
     
    Sign In to Vote
    0

    We have used IFD for the current project and it has worked fine when using HTML/Javascript/SilverLight as web resources. We have not faced any issues disucssed in the post. If a seperate site is implemented, ADFS token exchange will be a problem and that will lead to the issues discussed in the post. To avoid them, using resources as webresource is the way to go.