Re: [SOGo] Using resources with SQL-based authentication
We have successfully configured resources for SQL based user sources. I have updated SOGo wiki page: http://wiki.sogo.nu/ResourceConfiguration Igor Vitorac wrote, On 13/08/2012 11:19: Thanks. We will try to put some resources in place for SQL based user sources, and I will let you know about the results. Regards, Igor Vitorac Ludovic Marcotte wrote, On 12/08/2012 01:18: On 11/08/12 18:05, Igor Vitorac wrote: Thank you. I have seen that, but it is not quite clear what is the difference between two mentioned kinds (location and thing). A group, location or thing is a resource for SOGo - just like it's/was stated in the Schema for representing resources for calendaring and scheduling services (http://tools.ietf.org/html/draft-cal-resource-schema-06). When KindFieldName equals either of these for an entry (LDAP or SQL), SOGo considers it as a resource. Additionally confusing for me is a group kind. In LDAP, each group has to have a list of names, but how can we specify the users in one group if the user source is SQL? Once group defined, I guess, SOGo user could specify sharing permissions (ACLs) based on the group. This is something totally different. Groups are supported for LDAP (for scheduling meetings, ACLs, etc.) but not for SQL. -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Using resources with SQL-based authentication
Thanks. We will try to put some resources in place for SQL based user sources, and I will let you know about the results. Regards, Igor Vitorac Ludovic Marcotte wrote, On 12/08/2012 01:18: On 11/08/12 18:05, Igor Vitorac wrote: Thank you. I have seen that, but it is not quite clear what is the difference between two mentioned kinds (location and thing). A group, location or thing is a resource for SOGo - just like it's/was stated in the Schema for representing resources for calendaring and scheduling services (http://tools.ietf.org/html/draft-cal-resource-schema-06). When KindFieldName equals either of these for an entry (LDAP or SQL), SOGo considers it as a resource. Additionally confusing for me is a group kind. In LDAP, each group has to have a list of names, but how can we specify the users in one group if the user source is SQL? Once group defined, I guess, SOGo user could specify sharing permissions (ACLs) based on the group. This is something totally different. Groups are supported for LDAP (for scheduling meetings, ACLs, etc.) but not for SQL. -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Using resources with SQL-based authentication
Hi Ludovic, On 11/08/12 16:27, Dominique Dominique wrote: Let's be honest, the RTFM answer is a bit dry, but you're right we should pay closer attention to it. It's not dry, it's a fact. The documentation is there and we spend a great time writing it. If you think it can be improved, send improvements directly. And I love reading your manual, don't get me wrong. A good idea would be to identify clearly the changes in the manual - when an option is being introduced or modified or when it has been deprecated and/or replaced. That would make reading the manual more user friendly, update after update. We already mention new options when we make a release. Mentioning that over and over in the doc would clutter it. I know you do. But adding a pointer saying added or removed in version xxx would not clutter the document and make it easier to users to figure out why some options do not work anymore or since when it has been introduced, since the manual only refers to the last version. Many users jump versions when upgrading. I saw that part in recent version of the documentation, but It's less than obvious to derive from those pages that you have to create those two fields in the SQL table to be able to use the functionality. Furthermore the authentication table is provided by the application itself, so one could expect the columns to be already present - or to be part of the upgrade process as other table/columns are added/modified. You're wrong. The authentication table is not provided by SOGo at all. My bad. Isn't the sogo_view table a part of the program? It is actually mentioned page 27. In the documentation mentioned, several other fields are also optional - should they also be added to the same table? If they are mentioned as optional, why should they be added? Optional does not mean they could not be added, just not used. But that's how I read it. And including them directly with their definition (type and length) would help my limited and tired brain see the relation more easily with the manual. Furthermore, not all fields mentioned have a use in the table. Have a nice Sunday. Dominique-- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Using resources with SQL-based authentication
Hi, I second the request... My own request for info months ago got unanswered Dominique On 10/08/2012, at 18:14, Igor Vitorac igor.vito...@eurodyn.be wrote: Hi, We are trying to setup SOGo with SQL-based authentication, however we have not found any documentation or examples how to manage resources (e.g. meeting rooms) with SQL. There is a page dedicated in wiki, however section for SQL is empty: http://wiki.sogo.nu/ResourceConfiguration I would appreciate if anybody has any hints or examples? Many thanks, Igor Vitorac SOGo 1.3.17 -- users@sogo.nu https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Using resources with SQL-based authentication
On 11/08/12 12:32, Dominique Dominique wrote: I second the request... My own request for info months ago got unanswered You should read the documentation. Page 26 and 27 from the installation and configuration guide. Just create the KindFieldName and MultipleBookingsFieldName columns in your authentication table/view and set the values accordingly. -- Ludovic Marcotte +1.514.755.3630 :: www.inverse.ca Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Using resources with SQL-based authentication
Let's be honest, the RTFM answer is a bit dry, but you're right we should pay closer attention to it. A good idea would be to identify clearly the changes in the manual - when an option is being introduced or modified or when it has been deprecated and/or replaced. That would make reading the manual more user friendly, update after update. I saw that part in recent version of the documentation, but It's less than obvious to derive from those pages that you have to create those two fields in the SQL table to be able to use the functionality. Furthermore the authentication table is provided by the application itself, so one could expect the columns to be already present - or to be part of the upgrade process as other table/columns are added/modified. In the documentation mentioned, several other fields are also optional - should they also be added to the same table? I'll give it a try. But some examples would have been nice too. Dominique On 11/08/2012, at 20:11, Ludovic Marcotte lmarco...@inverse.ca wrote: On 11/08/12 12:32, Dominique Dominique wrote: I second the request... My own request for info months ago got unanswered You should read the documentation. Page 26 and 27 from the installation and configuration guide. Just create the KindFieldName and MultipleBookingsFieldName columns in your authentication table/view and set the values accordingly. -- Ludovic Marcotte +1.514.755.3630 :: www.inverse.ca Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Using resources with SQL-based authentication
On 11/08/12 16:27, Dominique Dominique wrote: Let's be honest, the RTFM answer is a bit dry, but you're right we should pay closer attention to it. It's not dry, it's a fact. The documentation is there and we spend a great time writing it. If you think it can be improved, send improvements directly. A good idea would be to identify clearly the changes in the manual - when an option is being introduced or modified or when it has been deprecated and/or replaced. That would make reading the manual more user friendly, update after update. We already mention new options when we make a release. Mentioning that over and over in the doc would clutter it. I saw that part in recent version of the documentation, but It's less than obvious to derive from those pages that you have to create those two fields in the SQL table to be able to use the functionality. Furthermore the authentication table is provided by the application itself, so one could expect the columns to be already present - or to be part of the upgrade process as other table/columns are added/modified. You're wrong. The authentication table is not provided by SOGo at all. In the documentation mentioned, several other fields are also optional - should they also be added to the same table? If they are mentioned as optional, why should they be added? -- Ludovic Marcotte +1.514.755.3630 :: www.inverse.ca Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Using resources with SQL-based authentication
On 11/08/12 18:05, Igor Vitorac wrote: Thank you. I have seen that, but it is not quite clear what is the difference between two mentioned kinds (location and thing). A group, location or thing is a resource for SOGo - just like it's/was stated in the Schema for representing resources for calendaring and scheduling services (http://tools.ietf.org/html/draft-cal-resource-schema-06). When KindFieldName equals either of these for an entry (LDAP or SQL), SOGo considers it as a resource. Additionally confusing for me is a group kind. In LDAP, each group has to have a list of names, but how can we specify the users in one group if the user source is SQL? Once group defined, I guess, SOGo user could specify sharing permissions (ACLs) based on the group. This is something totally different. Groups are supported for LDAP (for scheduling meetings, ACLs, etc.) but not for SQL. -- Ludovic Marcotte +1.514.755.3630 :: www.inverse.ca Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] Using resources with SQL-based authentication
Hi, We are trying to setup SOGo with SQL-based authentication, however we have not found any documentation or examples how to manage resources (e.g. meeting rooms) with SQL. There is a page dedicated in wiki, however section for SQL is empty: http://wiki.sogo.nu/ResourceConfiguration I would appreciate if anybody has any hints or examples? Many thanks, Igor Vitorac SOGo 1.3.17 -- users@sogo.nu https://inverse.ca/sogo/lists
