We use a third service for proxy storage/retrieval. The service stores pgtIou and pgtId pairs in a database. However, our main reason for using a separate app for pgt storage/retrieval has to do with the fact that we're using Rails, and in Rails controllers are synchronous, making it impossible to respond to a CAS proxy storage/retrieval request in the middle of an action.
Tom O'Brien wrote: > Hi folks, > > I'm just getting started with the CAS proxy approach and was > wondering if folks had preferences about whether to set the > pgtIou/pgtId pair as application variables that the proxying app can > access directly (I'm currently using my calling app as the > proxyCallbackURL as well), or whether the proxyCallbackUrl should > store these in a db for lookup by the proxying app. Is the former > dangerous (it seems like an SSL proxying app shouldn't need this step > if it can get the pair itself via the indirect method?) or is there > something else I should consider? > > Thanks! > > Tomo > > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas > This e-mail message is privileged, confidential and subject to copyright. Any unauthorized use or disclosure is prohibited. Le contenu du pr'esent courriel est privil'egi'e, confidentiel et soumis `a des droits d'auteur. Il est interdit de l'utiliser ou de le divulguer sans autorisation. _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
