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
