No, I am not trying to migrate from a hosting service. And this doesn't have anything to do with contacts. I don't know where you got either of those ideas.
The portal is hosted at Rackspace. HFS will run on a file server here in the Atlanta office.
I'll have no trouble creating a page within the portal that contains an iframe that refers to the HFS host here in Atlanta.
But, if that's
all I do, then when a portal user -
who has already logged into the portal - surfs to the page containing the iframe, he will see the HFS login challenge. This will (rightly) annoy him! He has already logged into the portal, why should he have to log in again?
I have no issue with creating accounts within HFS to exactly mirror the accounts in the portal. I have no issue with setting permissions on all these accounts to see the appropriate files/folders in the VFS.
I just want to be able to have the portal somehow "pass a parameter" to HFS to tell it who the currently-logged-in portal user is (e.g. in the iframe's URL), and then have HFS react by silently logging that user in and respecting their permissions.
Maybe it would entail composing the iframe URL something like:
http://hfs.mycompany.com:1234?user=fred
to tell HFS to connect to the "fred" account. This need not compromise security; I can arrange it that only calls coming from the portal's IP can connect through the Atlanta firewall to the HFS server. Thus I can be sure that calls are only made on behalf of already-authenticated portal users.
If there is no existing feature to let me get into HFS with a previously authenticated user name, can anyone advise me as to what it would take to add such a feature? What technologies and development resources does it take to (re)program HFS? It's open-source and we have programmers, but alternatively, would anyone care to undertake this enhancement for a fee?