The recommended approach is, whatever works for your environment. If your client needs SAML1, then use SAML1. If it needs attributes and your client supports CAS3, then use CAS3. If it needs attributes and your client does not support CAS3, use SAML1. It all depends on what type and version of a CAS client you run.
From: Manfredo Hopp [mailto:mhopp.coni...@gmail.com] Sent: Thursday, September 10, 2015 3:23 PM To: cas-user@lists.jasig.org Subject: [cas-user] SAML1 or Cas 20 or Cas30? Hi, in view of recent topics arised on cas20 releasing attributes I am trying to figure out which is the best way to handle migration to other protocols. We have cas 4.0 installed with SAML1 Validation. Here comes first point: is it worth changing protocol? If answer is yes then second point arises. 2 point moving to Cas 20: when moving to Cas20 using cas-client 3.3.3 i got the famous non released attributes problem. So after spending some time to make it work, James Winter's solution (Ref1) solved the problem. And here does point 3 arise: with problems showing up in point 2 (which involves changing cas source) we could think of moving to cas 30 directly. With no other requisits for different protocols than getting user attibutes released as a default behaviour which are the recommended steps. Thank you Manfredo Ref1: adding following to casServiceValidationSuccess.jsp: <c:forEach var="auth" items="${assertion.chainedAuthentications}"> <c:forEach var="attr" items="${auth.principal.attributes}" > <cas:${fn:escapeXml(attr.key)}>${fn:escapeXml(attr.value)}</cas:${fn:escapeXml(attr.key)}> </c:forEach> </c:forEach> -- You are currently subscribed to cas-user@lists.jasig.org <mailto:cas-user@lists.jasig.org> as: mmoay...@unicon.net <mailto:mmoay...@unicon.net> To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user -- You are currently subscribed to cas-user@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
