I just tried it again and worked great. cd applications mkdir provider mkdir consumer cp -r welcome/* provider cp -r welcome/* consumer edit consumer/models/db.py and replace Auth(db) with Auth(db,cas_provider='http://127.0.0.1:8000/provider/default/user/cas') open http://127.0.0.1:8000/provider # create an account and logout open http://127.0.0.1:8000/consumer # login
It does not require routes. It does not require anything else. Existing routes can break it if you point to the wrong URL in cas_provider. On Friday, 22 February 2013 12:59:11 UTC-6, rh wrote: > > On Thu, 21 Feb 2013 11:37:05 -0800 (PST) > Massimo Di Pierro > <[email protected] <javascript:>> wrote: > > > Not sure what example to write. > > > > Make two copies of the welcome app. Call one app1 and one app2. > > Create and account and login in app1. > > > > Edit app2/models/db.py and replace > > > > auth = Auth(db) > > > > with > > > > auth = Auth(db,cas_provider = > > 'http://127.0.0.1:8000/app1/default/user/cas') > > > > Now try login in app2. and you will get redirected to app1. > > Does this work for you or anyone else? > > I also grabbed the latest from github and still it's not working. > So far I tried a stable release from october and releases up to now. > I tried two separate alphas from github also. > > Any other advice? Does CAS require a routes.py? I will try that next > but really am close to throwing in the towel on this. Maybe it's not > used much so it has not had much coverage? I really don't know anything > about CAS and reading about it in the docs it made sense to me to keep > auth local and manageable via web2py. I see the ja-sig CAS server is java > so maybe that makes people not consider CAS? > > -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
