Carl Tyler's Blog

1 - In case you didn't notice, this isn't the case at IdeaJam. It takes a little massaging, but you can make the registrations available instantaneously. This isn't without a cost though, as you have to kill the cache that helps the perfromance of the name lookups. If I can get my act together, I will put a stand alone version up on OpenNTF.

2 - Hi Sean I realize that, and the sametime self reigstration db does the same, but here are the challenges for you.

Try that on a system where lets say 5-10 people are registering each minute.

Now, assign access to DBs etc for those people through group membership.

3 - @Sean, whats your method? I had some luck with updall api calls to the server... expensive.

@Carl, i so agree with you, you shouldn't have to massage anything. In your case its two fold, the authentication and authorization, a look up for the person then a look up to see if they're in the group.

I remember trouble shooting with people on the phone, to make it easier i used a ini parameter to tell the server which views to use for person and group looksups then added the views to the ui of the DD so i could do a quick Shift+F9 on them; to get it done ASAP.

4 - I assume this is partly related to your registration at BleedYellow? Part of the reason for this taking a few minutes is that we have a scheduled agent actually processing the registrations. The minimum time you can set an agent for is 5 minutes - hence the potential wait...

5 - @4 Yep it was my reminder of what Domino needs. By the way a little trick, where it says 5 minutes, just type in the number 1 and save, now it runs every minute

6 - Now do we REALLY want to do that? :) Patience my young padawans... I agree with the whole caching things, but generally new accounts are available pretty much immediately.

7 - Another option:
1. Don't Use the adminp - create users directly in the address book.
2. When adding the user to the access group also add him, with same access , to the db(s) ACL so he get the access immediately.
3. Run an agent every hour that remove new users from the ACL, of course you need to check that user exist more than X (cache time) minutes.

not very elegant but works and keep the server cache untouched.

8 - @7 Clever workaround! I wonder if the ACL note would become bloated with log entries ?

9 - Hey Guys

In the Admin session at LS they talked about the fact that we wont have to wait for the cache to flush for this stuff from 8.5

I know we will believe it when we see it, but I am only reporting what they said.

Cheers (in hope!)