External applications on a mainframe server.

[Ed HOLT]

Hi,

That explains it. Many thanks for the great support, much appreciated.

Regards,

Ed



-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: 13 October 2016 18:35
To: Shib Users <users at shibboleth.net>
Subject: RE: External applications on a mainframe server.

> Thanks for the quick response. For clarification, after putting in 
> https://sp.syspertec.com/virtel I go through and complete SSO and I 
> can then see a http request being sent to 
> https://virtel.syspertec.com:41002 ( the mainframe web server). That 
> responds OK. The next request from the browser is as follows:-

If you see a request to that port, it had better be from the proxy, not the
client.

The browser can access only the proxy.

> which fails with a 404  as /w2h/appmenu.htm+applist doesn't exist on 
> the SP, but lives on the mainframe web Server.

That doesn't matter. All the resources must virtually live on the proxy to
be proxied to the back-end. The client can only see the proxy and all the
URLs it requests have to be for that proxy.

> I have tried a test using a virtual
> host on the SP Apache and bypassing shibboleth. This works and I can 
> access my legacy applications via the mainframe web server. The only 
> difference I can see is that the Host header has 
> sp.syspertec.com:41002 but when going via shibboleth it just has
sp.syspetec.com and no port.

The SP is not causing that, it has no involvement in your proxying, that
happens after it's done its work for each request.

-- Scott


--
To unsubscribe from this list send an email to
users-unsubscribe at shibboleth.net