Hello All,
I have a question about how E-Sourcing initially brings up the login page. We are having an issue where we are going through a proxy for external vendors mapped to our Enterprise Cluster. When accessing the proxy externally, we get a certificate warning from the actual box that E-Sourcing resides on. After continuing through that warning, we receive the the login page like normal and can use the application without issue.
Basically, all the calls to the page are to our external 'alias' except one. Tracking a session with an HTTP watching tool, through a whole session, the only calls to our internal 'server name' was at the login page and then when loading the login page at logoff. For some reason, one call in the process of loading the login page makes a call specifically to our 'server name' instead of our alias. Is this a configuration change that we are missing to redirect or refresh the page that makeas a call to our internal server name?
As a quick example:
Internal Name: (sapeso1) https://sapeso1.companynetwork.com:<port>/sourcing/fsvendor/vendorsdesktop/login
External Name: (esourcing) https://esourcing.companyname.com/sourcing/fsvendor/vendordesktop/login
When using the external URL, all the HTTPS get calls uses esourcing.companyname.com/.../ except one, which uses sapeso1:<port>. After clicking through a certificate warning (since it's a self-signed cert for that machine that is trusted internally) the page continues making calls to esourcing.companyname.com/.../
I know this might be asking a lot, I'm just having trouble figuring out what exactly is happening when calling a page and loading the login. I've read through the docs, especially the directory config/cluster config, but couldn't figure out what we did wrong. Thanks for any help anyone can provide.
Derek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.