Hello,
I'm configuring Sharepoint 2013 to run behind a gateway. I'm using claims-based auth to sign in to the Sharepoint.
The SAML claim is fine, I can send it through to _trust/ and be signed in correctly, but only if I am on the local network and not going through the gateway. If I try to route through the gateway, with the exact same SAML claim, I am just bounced to the login page.
When running behind a proxy, are there particular settings that need configured in Sharepoint / IIS that I haven't accounted for? I've played with the AAM settings but got no luck.
Thanks,
Matt
EDIT: More info
A bit more info on what I'm trying to do:
I am using a gateway as a reverse proxy that sits in between the SharePoint server, the sequence is something like this:
1) User -> Reverse Proxy <-> Validate user credentials via some method (not AD)
2) Reverse Proxy <-> Submits RST request to 3rd Party STS, returning a SAML token
3) Reverse Proxy <-> Forwards SAML token to SharePoint application configured for claims
4) User <- Reverse Proxy returns content to user from SharePoint
Instead of returning the SharePoint content, SharePoint redirects me to screen to select how I want to sign-in.
So why would SharePoint do this?
Thanks,
Matt