Mailing List Archive: newbie thoughts and questions

davical-0.9.7.6-0.noarch.rpm

First - great program

Second - I got LDAP authentication working and the 'Sync LDAP w/ RCDS'
was just friggen awesome.

So I immediately ran into an issue where the 'Sync LDAP w/ RCDS'
disabled user 1 'admin' which was a problem because I no longer had an
administrator. I solved this in postgres with the command...
INSERT into role_member (role_no, user_no) VALUES (1, 1010);
but it definitely seems to me that in no case should this action disable
the login for user #1

Now I am intrigued by the LDAP option of...
"user_no" => "uidNumber" , // set DAViCal user no to match Unix uid
from LDAP

but if I create 'resource' calendars manually, they will be put into the
same 1000 (1001, etc) range as my uid's so I will have a clash and if I
import users before I create 'resource' calendars, then I won't have the
option to subscribe them to the calendars upon creation. So I looked but
I couldn't see any way to specify the userID numbers for new calendars
so I could have 'resource' calendars numbered in a lower range so as not
to clash. I am definitely afraid to start tweaking them in postgres
because I might miss a related entry in another table. Am I missing
something?

Craig

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

On Sun, 2009-11-01 at 21:36 -0700, Craig White wrote:
> davical-0.9.7.6-0.noarch.rpm
>
> First - great program
>
> Second - I got LDAP authentication working and the 'Sync LDAP w/ RCDS'
> was just friggen awesome.
>
> So I immediately ran into an issue where the 'Sync LDAP w/ RCDS'
> disabled user 1 'admin' which was a problem because I no longer had an
> administrator. I solved this in postgres with the command...
> INSERT into role_member (role_no, user_no) VALUES (1, 1010);
> but it definitely seems to me that in no case should this action disable
> the login for user #1

You're probably right. I'm surprised nobody has pointed the problem out
to me before, but I'd be happy to see a patch stopping it from modifying
user 1.

Now that there's an option to delete users anyone who wanted that user
gone could do so.

> Now I am intrigued by the LDAP option of...
> "user_no" => "uidNumber" , // set DAViCal user no to match Unix uid
> from LDAP
>
> but if I create 'resource' calendars manually, they will be put into the
> same 1000 (1001, etc) range as my uid's so I will have a clash and if I
> import users before I create 'resource' calendars, then I won't have the
> option to subscribe them to the calendars upon creation. So I looked but
> I couldn't see any way to specify the userID numbers for new calendars
> so I could have 'resource' calendars numbered in a lower range so as not
> to clash. I am definitely afraid to start tweaking them in postgres
> because I might miss a related entry in another table. Am I missing
> something?

The straightforward way would be to go into PostgreSQL and set the
sequence to somewhere that won't collide with your range:

SELECT setval('usr_user_no_seq', 31415926536);

Or perhaps some more rational number... :-)

Cheers,
Andrew.

------------------------------------------------------------------------
andrew (AT) morphoss (DOT) com +64(272)DEBIAN
Too much is just enough.
-- Mark Twain, on whiskey
------------------------------------------------------------------------

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <http://lists.morphoss.com/pipermail/davical-users/attachments/20091102/a55918c6/attachment.pgp>
-------------- next part --------------