I believe this has been fixed in trunk. Can you check? If you confirm we will deploy a new web2py version.
On Wednesday, 6 April 2016 08:55:31 UTC-5, Franz Pietz wrote: > > Same here. My server was running 2.12.3 and CAS works fine (with a logout > issue that I reported previously, but had no answer yet). > > After updating to 2.14.3, I get the same 'not authorized' page. > > On Saturday, April 2, 2016 at 4:15:04 AM UTC-3, mweissen wrote: >> >> Is cas broken in 2.14.3? >> >> I am not sure - I have tested it with two different sites and I have got >> errors like "invalid request" or "not authorized". >> >> Site 1: Cas worked before upgrade to 2.14.3. >> >> Site 2: A new test with my local server: >> >> In application m_abschluss, db.py: >> >> auth = Auth(db, cas_provider = ' >> http://127.0.0.1:8000/media/default/user/cas') >> >> >> A login to m_abschluss creates this url: >> >> >> http://127.0.0.1:8000/media/default/user/cas/login?service=http://127.0.0.1:8000/m_abschluss/default/user/login >> >> And a call to this url gives "not authorized". >> >> Kind regards, Martin >> >> >> -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
