[Anthill-pro] Notifying a single user

Wed Mar 7 22:06:42 CST 2007

I get the following error.

Tate Jones

-----Original Message-----
From: anthill-pro-bounces at caladin.urbancode.com
[mailto:anthill-pro-bounces at caladin.urbancode.com] On Behalf Of Eric
Minick
Sent: Thursday, 8 March 2007 2:52 AM
To: anthill-pro at caladin.urbancode.com
Subject: Re: [Anthill-pro] Notifying a single user

Hi All,

Just a quick correction. I had the wrong method name in my most recent 
example, the example should have been:

userFactory = UserFactory.getInstance();
result = new User[] {
  userFactory.restoreForName("my_user")
};

Thanks,

Eric

Eric Minick wrote:

> Curtis and Tate,
>
> The Anthill realm won't include the LDAP users. In 3.1, all LDAP users

> will be from a realm called 'LDAP'. Anthill knows about them, but it 
> also knows that they come from LDAP, and all the security credentials 
> remain there. The realm name is a bit under the covers in 3.1 and only

> really important in scripting.
>
> In 3.2, this changes. Anthill based authentication is still the 
> 'Anthill' realm, but LDAP, etc are each given a realm name at 
> configuration time. So if you have 'Jane Doe' from one authentication 
> source and another 'Jane Doe' from another, they won't collide.
>
> So if you want to pick a specific user, you need to tell Anthill a 
> little about where it's coming from, or at least you should. My 
> example could have been:
>
> userFactory = UserFactory.getInstance();
> result = new User[] {
>   userFactory.restoreForNameAndRealm("my_user")
> };
>
> This would have taken the first user matching that name regardless of 
> realm. Actually, for 90% of people, that's going to be perfectly fine.

> It's just a little sloppier.
>
> One more tidbit, the 'admin' user lives in the 'System' realm in case 
> you want to mail that address.
>
> Thanks,
>
> Eric
>
> Curtis Yanko wrote:
>
>>
>> If I may. I thought that once someone logged in and we authenticated 
>> against LDAP that they did exist within the Anthill 'realm' or that 
>> an Anthill 'realm' account was created. Otherwise how would I map 
>> alias and emails to it? Additionally, if I am to use AHP for 
>> Authorization I need that AHP 'realm' user' to do it with.
>>
>> - Curtis Yanko
>> United Health Technologies
>> Mail Route: CT028-06SA
>> Internet email: curt_yanko at uhc.com
>> Office 860.702.9059
>> Cell 860.729.8171
>>
>>
>>
>> *Maciej Zawadzki <mbz at urbancode.com>*
>> Sent by: anthill-pro-bounces at caladin.urbancode.com
>>
>> 03/07/2007 09:40 AM
>> Please respond to
>> anthill-pro at caladin.urbancode.com
>>
>>
>>     
>> To
>>     anthill-pro at caladin.urbancode.com
>> cc
>>     anthill-pro at caladin.urbancode.com
>> Subject
>>     Re: [Anthill-pro] Notifying a single user
>>
>>
>>
>>     
>>
>>
>>
>>
>>
>> > Does this mean "my_user" must exist in LDAP?
>>
>> In the script example that Eric gave below the "my"user" is being
pulled
>> from the LDAP realm -- but the user could just as easily have been
>> pulled from the "Anthill" realm, in which case the user would not
need
>> to exist in LDAP.
>>
>> The big point is that in 3.2, you will be able to have some Anthill
>> users that come from LDAP and others that are configured right in
>> Anthill (and thus do not need to exist in LDAP).  So it will be easy
to
>> do what you're asking about.
>>
>> Regards,
>>
>> --Maciej
>>
>>
>> >
>> > Tate Jones
>> >
>> > -----Original Message-----
>> > From: anthill-pro-bounces at caladin.urbancode.com
>> > [mailto:anthill-pro-bounces at caladin.urbancode.com] On Behalf Of
Eric
>> > Minick
>> > Sent: Wednesday, 7 March 2007 10:05 AM
>> > To: anthill-pro at caladin.urbancode.com
>> > Subject: Re: [Anthill-pro] Notifying a single user
>> >
>> > Tate,
>> >
>> > The good news is that in version 3.2 you'll be able to use the
Anthill
>> > authentication scheme alongside LDAP.
>> >
>> > Selecting a single user from the notification scheme requires a
script
>> > like:
>> >
>> > import com.urbancode.anthill3.domain.security.*;
>> >
>> > userFactory = UserFactory.getInstance();
>> > result = new User[] {
>> >   userFactory.restoreForNameAndRealm("my_user","my_ldap_realm")
>> > };
>> >
>> >
>> >
>> > Does that answer the question adaquately? The trick to note is that

>> your
>> >
>> > script has to return an array of users, other than that, it's 
>> relatively
>> >
>> > straight forward.
>> >
>> > -- Eric
>> >
>> >
>> > Jones, Tate wrote:
>> >
>> >> Everybody in the development team develops on a generic build
machine
>> >> and logon account, however they commit using their individual user
>> >> ids. I want to be able to notify a generic user id for build
>> >> notifications using IM. I cannot add another user to Anthill as we

>> are
>> >
>> >> using LDAP. Can I create a simple script to return a User object
in
>> >> the "User Generator" screen or force the IM script to notify a
>> >> specific user?
>> >>
>> >> Eg. User("developer")
>> >>
>> >> Tate Jones | Engineering Manager | +61-7-32274469 |
>> >> tjones at rsasecurity.com <mailto:tjones at rsasecurity.com%20>
>> >>
>> >> Level 32, Waterfront Place, 1 Eagle Street, Brisbane QLD 4001 |
>> >> www.rsasecurity.com <http://www.rsasecurity.com/>** ******
>> >>
>> >> **
>> >>
>> >> 
>>
-----------------------------------------------------------------------
>> > -
>> >> _______________________________________________
>> >> Anthill-pro mailing list
>> >> Anthill-pro at lists.urbancode.com
>> >> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>> >>
>> >>
>> >
>> > _______________________________________________
>> > Anthill-pro mailing list
>> > Anthill-pro at lists.urbancode.com
>> > http://lists.urbancode.com/mailman/listinfo/anthill-pro
>> > _______________________________________________
>> > Anthill-pro mailing list
>> > Anthill-pro at lists.urbancode.com
>> > http://lists.urbancode.com/mailman/listinfo/anthill-pro
>> >
>> _______________________________________________
>> Anthill-pro mailing list
>> Anthill-pro at lists.urbancode.com
>> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>>
>>
>> This e-mail, including attachments, may include confidential and/or
>> proprietary information, and may be used only by the person or entity
to
>> which it is addressed. If the reader of this e-mail is not the
intended
>> recipient or his or her authorized agent, the reader is hereby
notified
>> that any dissemination, distribution or copying of this e-mail is
>> prohibited. If you have received this e-mail in error, please notify
the
>> sender by replying to this message and delete this e-mail
immediately.
>>
>>
------------------------------------------------------------------------
>>
>> _______________________________________________
>> Anthill-pro mailing list
>> Anthill-pro at lists.urbancode.com
>> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>>  
>>
>
> _______________________________________________
> Anthill-pro mailing list
> Anthill-pro at lists.urbancode.com
> http://lists.urbancode.com/mailman/listinfo/anthill-pro

_______________________________________________
Anthill-pro mailing list
Anthill-pro at lists.urbancode.com
http://lists.urbancode.com/mailman/listinfo/anthill-pro