[Info-vax] LDAP

[Kerry Main]

> -----Original Message-----
> From: Info-vax <info-vax-bounces at rbnsn.com> On Behalf Of Jan-Erik
> Söderholm via Info-vax
> Sent: October 7, 2020 8:14 PM
> To: info-vax at rbnsn.com
> Cc: Jan-Erik Söderholm <jan-erik.soderholm at telia.com>
> Subject: [Info-vax] LDAP
> 
> Hi.
> 
> I have been asked if we can use LDAP against the corporate AD systems to
> authenticate our user logins to our OpenVMS system.
> 
> Currently on VSI/Alpha.
> 
> Anyone that have looked and/or tested these LDAP parts on Alpha?
> And if so, any thoughts, findings or something else worth to report?
> How does it work with a mixed LDAP/local password verification?
> 
> The users to be verified over LDAP/AD are those that have “personal”
> VMS accounts using their corporate signature. We also have “workgroup”
> accounts for the workplaces in the factory, and they are not in the AD.
> 
> The logins are done using plain telnet sessions from terminal emulators.
> No ssh here, if that matters in regard to LDAP

> 
> Just starting to look at this

> 
> Regards, Jan-Erik.

For those familiar with Windows environments, think of global AD (aka LDAP)
and local Windows (aka sysuaf) user accounts.

Something else to consider:
<http://www.process.com/products/vam/index.html> 
<http://www.process.com/products/vam/vam_spd.html>

Extract:
" The VMS Authentication Module (VAM) provides controlled access to both
user-written applications and the OpenVMS system overall using LDAP, RADIUS
or the local VMS User Authentication File (UAF). It can be incorporated into
an OpenVMS-based platform in three ways:
- Via an API that can be incorporated into an application to control access
to that application
- On a system-wide basis by using the OpenVMS ACME system on OpenVMS V8 and
higher on Alpha and Integrity platforms
- On a system-wide basis via use of the LGI callouts for OpenVMS
LOGINOUT.EXE. "

Regards,

Kerry Main
Kerry dot main at starkgaming dot com