Hello all, does anybody (Scott? ^^) have any example for such an implementation and the steps needed to achieve this? If anybody could help me implementing this I would be pleased to summarize the steps for the CAS WIKI.
I think it would be a good addition to the CAS documentation... ;) Thx in advance! Arthur On Mon, 2008-09-29 at 09:40 -0400, Scott Battaglia wrote: > Arthur, > > We actually see this come up every so often. Our recommendation has > always been that the application that does the user registration > should generate a sufficiently long random identifier and store it in > a database in combination with the username and an expiration date. > The application should then pass that identifier to the CAS login > page. > > CAS should be configured to read the token and construct a credentials > object from it. A combination of authentication handler/ > credentialstoprincipal resolver would be able to read from the DB, see > the username, and remove the token. > > -Scott > > -Scott Battaglia > PGP Public Key Id: 0x383733AA > LinkedIn: http://www.linkedin.com/in/scottbattaglia > > > On Mon, Sep 29, 2008 at 4:47 AM, Arthur Erdös <[EMAIL PROTECTED]> > wrote: > Hello all, > > is it possible to automatically authenticate an user at CAS > after he > submitted a registration form? I don't want the user to > authenticate > himself again, if he just registered... > > Kind regards, > Arthur > > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas > > _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
