[Info-vax] Externally authenticated users

Michael D. Ober obermd. at .alum.mit.edu.nospam.
Wed Jan 7 20:04:00 EST 2009


"Syltrem" <syltremzulu at videotron.ca> wrote in message 
news:TpU8l.77761$zQ4.57169 at en-nntp-02.dc1.easynews.com...
>
> "Malcolm Dunnett" <nothome at spammers.are.scum> a écrit dans le message de 
> news: 4963ee55 at flight...
>
>> SYS$ACM automagically handles externally authenticated users, unless you
>> override it by supplying an item of ACME$_TARGET_DOI_NAME with a value of 
>> "VMS" as one of the itemlist items in the call.
>>
>> Explicitly specifying the VMS DOI item to $ACM is the equivalent of
>> using the "/LOCAL" login switch.
>>
>> BTW Are you using the Microsoft DOI (Pathworks) or LDAP for the external 
>> accounts? I've been using LDAP here quite successfully (authenticating 
>> against Active Directory)
>
> Thank you very much for the information. This is quite helpful and exactly 
> what I was looking for. I have forwarded it to my vendor.
>
> I tried both Pathworks and LDAP and my application behaves the same way 
> with both.
> Since I have an Integrity server in my cluster - which can form a cluster 
> all by itself if need be - I settled to use LDAP. The authentication 
> server is Windows AD.
>
> Regards,
> Syltrem
>

The LDAP/AD integration works well.  I just wish HP would allow multiple 
LDAP servers, so when you're doing the monthly MS updates, you can still 
authenticate.

Mike.





More information about the Info-vax mailing list