Sign in
 
HomeSharePoint Server 2010SharePoint Foundation 2010LibraryForums
SharePoint Products TechCenter > SharePoint Products and Technologies Forums > SharePoint - Business Data Catalog (pre-SharePoint 2010) > Define the connected user in BDC
Ask a questionAsk a question
Search Forums:
 

AnswerDefine the connected user in BDC

Answers

  • Friday, October 02, 2009 1:01 PMBrian Bedard Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    The BDC only surfaces information from the LOB.

    If you use PassThrough, it will use the credentials of the logged in user to communicate with the backend system.  If the LOB is on another server (most likely it is) PassThrough won't work because of the double hop issue.  The WFE can't impersonate credentials for the logged in user.  The buck stops at the WFE.
    If you use RevertToSelf, it will use the credentials of the running webparts web application pool identity.
    If you use a DbProvider SqlServer and PassThrough and provide RdbUsername and RdbPassword, it will attempt to connect as that SqlServer user.
    If you use SingleSignOn and provide the application id, it will use the SSO database and provider to connect to the LOB as that user.

    Is this what you wanted?
     

All Replies

  • Wednesday, September 30, 2009 11:11 AMMayrun Digmi Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    What do you exactly mean?
     
  • Wednesday, September 30, 2009 6:33 PMLegna Rodama Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    YEA, what exactly... what the other guy said :-)

    Are you by any chance refering to SSO?

    Regards,
    Legna
     
  • Friday, October 02, 2009 1:01 PMBrian Bedard Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    The BDC only surfaces information from the LOB.

    If you use PassThrough, it will use the credentials of the logged in user to communicate with the backend system.  If the LOB is on another server (most likely it is) PassThrough won't work because of the double hop issue.  The WFE can't impersonate credentials for the logged in user.  The buck stops at the WFE.
    If you use RevertToSelf, it will use the credentials of the running webparts web application pool identity.
    If you use a DbProvider SqlServer and PassThrough and provide RdbUsername and RdbPassword, it will attempt to connect as that SqlServer user.
    If you use SingleSignOn and provide the application id, it will use the SSO database and provider to connect to the LOB as that user.

    Is this what you wanted?