Hello folks, Please advise me what is the best way to authenticate Windows AD users against Linux machines.
Currently I am going to take a look of Vintela Authentication Services and please let me know if you have experience with VIntela.
Thanks in advance (1 Reply)
Hi folks,
How can i configure an AIX LDAP client to authenticate against an Linux Openldap server over TLS/SSL?
It works like a charm without TLS/SSL.
i would like to have SSL encrypted communication for ldap (secldapclntd) and ldapsearch etc. while accepting every kind of certificate/CA.... (6 Replies)
I have customer who controls access to the internet via TACACS server, basically a PIX firewall uses authentication from the TACACS to say if traffic is allowed to pass out of the gateway. I can't find anything on how to configure a linux client of TACACS authentication only how to set up a linux... (1 Reply)
First, let me start off saying this is not spam. This is me trying to help out other AIX Admins with MS AD servers. If it is not applicable to you, someone else will find it useful.
As long as the "KDC" service is running on your AD server, these steps should work. There should be no... (3 Replies)
dminfo(1M) System Administration Commands dminfo(1M)NAME
dminfo - report information about a device entry in a device maps file
SYNOPSIS
dminfo [-v] [-a] [-f pathname]
dminfo [-v] [-a] [-f pathname] -n dev -name...
dminfo [-v] [-a] [-f pathname] -d dev -path...
dminfo [-v] [-a] [-f pathname] -t dev -type...
dminfo [-v] [-f pathname] -u dm -entry
DESCRIPTION
dminfo reports and updates information about the device_maps(4) file.
OPTIONS
The following options are supported
-a Succeed if any of the requested entries are found. If used with -v, all entries that match the requested case(s)
are printed.
-d dev-path Search by dev-path. Search device_maps(4) for a device special pathname in the device_list field matching the
dev-path argument. This option cannot be used with -n, -t or -u.
-f pathname Use a device_maps file with pathname instead of /etc/security/device_maps.
-n dev-name Search by dev-name. Search device_maps(4) for a device_name field matching dev-name. This option cannot be used
with -d, -t or -u.
-t dev-type Search by dev-type. Search device_maps(4) for a device_type field matching the given dev-type. This option cannot
be used with -d, -n or -u.
-u dm-entry Update the device_maps(4) file. This option is provided to add entries to the device_maps(4) file. The dm-entry
must be a complete device_maps(4) file entry. The dm-entry has fields, as in the device_maps file. It uses the
colon (:) as a field separator, and white space as the device_list subfield separators. The dm-entry is not made if
any fields are missing, or if the dm-entry would be a duplicate. The default device maps file can be updated only
by the super user.
-v Verbose. Print the requested entry or entries, one line per entry, on the standard output. If no entries are speci-
fied, all are printed.
EXIT STATUS
0 Successful completion.
1 Request failed.
2 Incorrect syntax.
FILES
/etc/security/device_maps
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO bsmconv(1M), device_maps(4), attributes(5)NOTES
The functionality described in this man page is available only if the Basic Security Module (BSM) has been enabled. See bsmconv(1M) for
more information.
SunOS 5.10 6 May 1993 dminfo(1M)