[web2py] Re: Wep2Py Database Tables
On Tuesday, May 29, 2012 8:30:47 PM UTC-4, Horus wrote: > > Having authentication as a core and apps built around it rather than every > app having its own admin/CAS > That's basically the idea of CAS, though each app that accesses the CAS provider still has to instantiate Auth in order to provide the functionality to authenticate against the provider. Anthony
[web2py] Re: Wep2Py Database Tables
Having authentication as a core and apps built around it rather than every app having its own admin/CAS On Monday, May 28, 2012 9:38:51 PM UTC-4, Anthony wrote: > > Not sure what you mean. > > On Monday, May 28, 2012 9:16:27 PM UTC-4, Horus wrote: >> >> ok understood. what do you think about having auth outside of the app? >> >> On Sunday, May 27, 2012 9:16:17 PM UTC-4, Anthony wrote: >>> >>> By default, instantiating Auth() automatically makes the application a >>> CAS provider, whether or not you actually use the app as a CAS provider. >>> So, if the app is not used as a provider, that table will simply remain >>> empty. If you want to prevent it from being created in the first place, >>> before calling auth.define_tables(), you can do: >>> >>> auth.settings.cas_domains = None >>> >>> Anthony >>> >>> On Sunday, May 27, 2012 2:13:25 PM UTC-4, Horus wrote: I know a bit about CAS single sign-on, however if each app is giving a different ACL database. Is the concept still being adhered to? I was under the assumption the single sign-on meant one (1) authentication gateway i.e. one auth database used by many applications. On Saturday, May 26, 2012 1:37:09 PM UTC-4, Niphlod wrote: > > it's for Central Authentication Services > > > http://web2py.com/books/default/chapter/29/9#Central-Authentication-Service > > Il giorno sabato 26 maggio 2012 18:46:26 UTC+2, Horus ha scritto: >> >> In the administrative section of your app there are the usual ACL >> tables. I realise there is a *acl_cas* table along with these >> tables. I am curious as to what this tables does? > >
[web2py] Re: Wep2Py Database Tables
Not sure what you mean. On Monday, May 28, 2012 9:16:27 PM UTC-4, Horus wrote: > > ok understood. what do you think about having auth outside of the app? > > On Sunday, May 27, 2012 9:16:17 PM UTC-4, Anthony wrote: >> >> By default, instantiating Auth() automatically makes the application a >> CAS provider, whether or not you actually use the app as a CAS provider. >> So, if the app is not used as a provider, that table will simply remain >> empty. If you want to prevent it from being created in the first place, >> before calling auth.define_tables(), you can do: >> >> auth.settings.cas_domains = None >> >> Anthony >> >> On Sunday, May 27, 2012 2:13:25 PM UTC-4, Horus wrote: >>> >>> I know a bit about CAS single sign-on, however if each app is giving a >>> different ACL database. Is the concept still being adhered to? >>> I was under the assumption the single sign-on meant one (1) >>> authentication gateway i.e. one auth database used by many applications. >>> >>> >>> On Saturday, May 26, 2012 1:37:09 PM UTC-4, Niphlod wrote: it's for Central Authentication Services http://web2py.com/books/default/chapter/29/9#Central-Authentication-Service Il giorno sabato 26 maggio 2012 18:46:26 UTC+2, Horus ha scritto: > > In the administrative section of your app there are the usual ACL > tables. I realise there is a *acl_cas* table along with these tables. > I am curious as to what this tables does?
[web2py] Re: Wep2Py Database Tables
ok understood. what do you think about having auth outside of the app? On Sunday, May 27, 2012 9:16:17 PM UTC-4, Anthony wrote: > > By default, instantiating Auth() automatically makes the application a CAS > provider, whether or not you actually use the app as a CAS provider. So, if > the app is not used as a provider, that table will simply remain empty. If > you want to prevent it from being created in the first place, before > calling auth.define_tables(), you can do: > > auth.settings.cas_domains = None > > Anthony > > On Sunday, May 27, 2012 2:13:25 PM UTC-4, Horus wrote: >> >> I know a bit about CAS single sign-on, however if each app is giving a >> different ACL database. Is the concept still being adhered to? >> I was under the assumption the single sign-on meant one (1) >> authentication gateway i.e. one auth database used by many applications. >> >> >> On Saturday, May 26, 2012 1:37:09 PM UTC-4, Niphlod wrote: >>> >>> it's for Central Authentication Services >>> >>> >>> http://web2py.com/books/default/chapter/29/9#Central-Authentication-Service >>> >>> Il giorno sabato 26 maggio 2012 18:46:26 UTC+2, Horus ha scritto: In the administrative section of your app there are the usual ACL tables. I realise there is a *acl_cas* table along with these tables. I am curious as to what this tables does? >>> >>>
[web2py] Re: Wep2Py Database Tables
By default, instantiating Auth() automatically makes the application a CAS provider, whether or not you actually use the app as a CAS provider. So, if the app is not used as a provider, that table will simply remain empty. If you want to prevent it from being created in the first place, before calling auth.define_tables(), you can do: auth.settings.cas_domains = None Anthony On Sunday, May 27, 2012 2:13:25 PM UTC-4, Horus wrote: > > I know a bit about CAS single sign-on, however if each app is giving a > different ACL database. Is the concept still being adhered to? > I was under the assumption the single sign-on meant one (1) authentication > gateway i.e. one auth database used by many applications. > > > On Saturday, May 26, 2012 1:37:09 PM UTC-4, Niphlod wrote: >> >> it's for Central Authentication Services >> >> >> http://web2py.com/books/default/chapter/29/9#Central-Authentication-Service >> >> Il giorno sabato 26 maggio 2012 18:46:26 UTC+2, Horus ha scritto: >>> >>> In the administrative section of your app there are the usual ACL >>> tables. I realise there is a *acl_cas* table along with these tables. I >>> am curious as to what this tables does? >> >>
[web2py] Re: Wep2Py Database Tables
I know a bit about CAS single sign-on, however if each app is giving a different ACL database. Is the concept still being adhered to? I was under the assumption the single sign-on meant one (1) authentication gateway i.e. one auth database used by many applications. On Saturday, May 26, 2012 1:37:09 PM UTC-4, Niphlod wrote: > > it's for Central Authentication Services > > http://web2py.com/books/default/chapter/29/9#Central-Authentication-Service > > Il giorno sabato 26 maggio 2012 18:46:26 UTC+2, Horus ha scritto: >> >> In the administrative section of your app there are the usual ACL tables. >> I realise there is a *acl_cas* table along with these tables. I am >> curious as to what this tables does? > >
[web2py] Re: Wep2Py Database Tables
it's for Central Authentication Services http://web2py.com/books/default/chapter/29/9#Central-Authentication-Service Il giorno sabato 26 maggio 2012 18:46:26 UTC+2, Horus ha scritto: > > In the administrative section of your app there are the usual ACL tables. > I realise there is a *acl_cas* table along with these tables. I am > curious as to what this tables does?
