Link to home
Start Free TrialLog in
Avatar of mgudites1
mgudites1Flag for United States of America

asked on

Authenticating to one web site from another

Here's the situation...I've got a Sharepoint site.  In that Sharepoint site, in a content editor web part (HTML), I'm trying to pull in content (images) from *another* IIS web site, which has Windows Authentication enabled.  What I'd like is for people who are already authenticated to the Sharepoint server, to be able to view the images in the content editor web part (I want the Sharepoint page to pass a username/password to the other server).  Is this possible?  

I've Googled up and down and I'm sure there's a way, I'm just not sure what to look for.
ASKER CERTIFIED SOLUTION
Avatar of RaithZ
RaithZ
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of mgudites1

ASKER

Sorry, I'm not looking to pass the user's authentication.  I want to pass a specific username and password.  

So, jsmith logs on to Sharepoint, and then when they go to this site, and they try to load up this page, Sharepoint passes a "hardcoded" username/password for an account called "pictures," which lives on the other server it's authenticating to.  Does that make sense?
Sorry I failed to read your question in full.  I would think this is possible but it would either need to be passed in the URL that the webpart pulls up or you would need to make a custom web part.  There is a SharePoint service called BCS but I don't think it would help in this particular situation.
I thought about the passing via the URL, but it would appear that solution doesn't work with IE.  Otherwise that would have been great.  It's a resource that we don't necessarily want the outside world having access to, but nothing so secure that if someone got a hold of the PW, would be a big deal.
You could check what authentication the SharePoint server gives your secondary resource and then give that ID permissions to the resource.  Check the logs on the destination server when authentication fails to see what credentials it tried to use.