Sure thing. For what it is worth, I think the .NET CAS Client dynamically generates the callback url based on the initial CAS request that comes in (from the app pool's start-up/recycle), so it is possible that both could be acceptable at different times. (One would have to go through the apps code to see what entry points are possible).
Both addresses should work. On 10/1/14 10:16 AM, Stephen Tyson wrote: > Yes, You are correct I was reviewing the CAS logs and the CAS admin seen the > invalid proxy chain. > > The instructions say to add https://webAddress/coa to the allowed proxy but > then states to use https://webAddress/coa/auth as the URL for the end user. > The logs were saying /coa/auth was an invalid proxy chain. We ended up > putting in /coa and /coa/auth for allowed proxy chains. > > Well we just tested and the solution is now working across all servers in > Dev. Now on to prod. > > I really appreciate you getting back to me so quickly. > > Thanks again > Stephen -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
