It would be fantastic if we could put an effective notice on the protocol docs about the best practice being to use the libraries.
I know someone is barking up the wrong tree when they start asking me 'are you using CAS1.0 or CAS2.0' questions. I have to convince them not to write code to the protocol, but to use the libraries, which is sometimes a hard sell. Best, Kim Kim Cary Chief Information Security Officer Pepperdine University On Sep 27, 2011, at 5:39 AM, Marvin Addison wrote: >> So far, the log in authenticates and a ticket is generated. >> The ticket is then sent to the "serviceValidate" process/page and an XML >> response is received. > > There's no reason to interact with CAS at that level, particularly for > new users, unless it's purely for academic study. For production > integration scenarios you should concentrate on integrating your > application with CAS using any number of existing software components. > See https://wiki.jasig.org/display/CASC/Home for a list; I would draw > your attention to the .NET client since you mentioned ASP. > > M > > -- > 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 <html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">It would be fantastic if we could put an effective notice on the protocol docs about the best practice being to use the libraries.<div><br></div><div>I know someone is barking up the wrong tree when they start asking me 'are you using CAS1.0 or CAS2.0' questions. I have to convince them not to write code to the protocol, but to use the libraries, which is sometimes a hard sell.<div><br><div> <span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div>Best,</div><div>Kim</div><div><br></div><div><br></div><div>Kim Cary</div><div>Chief Information Security Officer</div><div>Pepperdine University</div><div><br></div></span><br class="Apple-interchange-newline"> </div> <br><div><div>On Sep 27, 2011, at 5:39 AM, Marvin Addison wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><blockquote type="cite">So far, the log in authenticates and a ticket is generated.<br></blockquote><blockquote type="cite">The ticket is then sent to the "serviceValidate" process/page and an XML response is received.<br></blockquote><br>There's no reason to interact with CAS at that level, particularly for<br>new users, unless it's purely for academic study. For production<br>integration scenarios you should concentrate on integrating your<br>application with CAS using any number of existing software components.<br> See <a href="https://wiki.jasig.org/display/CASC/Home";>https://wiki.jasig.org/display/CASC/Home</a> for a list; I would draw<br>your attention to the .NET client since you mentioned ASP.<br><br>M<br><br>-- <br>You are currently subscribed to <a href="mailto:[email protected]";>[email protected]</a> as: <a href="mailto:[email protected]";>[email protected]</a><br>To unsubscribe, change settings or access archives, see <a href="http://www.ja-sig.org/wiki/display/JSG/cas-user";>http://www.ja-sig.org/wiki/display/JSG/cas-user</a><br></div></blockquote></div><br></div></div></body></html> -- 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
