Here is the info I was given from Quest/Dell technical support...
You will need to run this first:
/opt/quest/bin/vastool configure pam sys-auth
[0] [sellswor@vasdev-aix61] [~/pamAuth]
...
2016-04-12 14:07:30 (98.3 MB/s) - 'pamAuth.tar.gz' saved [1958]
[0] [sellswor@vasdev-aix61] [~/pamAuth]
$ tar xvzf pamAuth.tar.gz
Makefile
pamAuth.c
[0] [sellswor@vasdev-aix61] [~/pamAuth]
$ make
gcc -g -DAIX -o pamAuth pamAuth.c -lpam
[0] [sellswor@vasdev-aix61] [~/pamAuth]
$ ls
Makefile pamAuth pamAuth.c pamAuth.tar.gz [0] [sellswor@vasdev-aix61] [~/pamAuth] $ ./pamAuth
Usage: ./pamAuth <name> <password>.
[1] [sellswor@vasdev-aix61] [~/pamAuth]
$ ./pamAuth tu-6-1 Test1234
PAM_AUTH_SUCCES ( Good authentication )
[0] [sellswor@vasdev-aix61] [~/pamAuth]
It defaults to sys-auth as the name, they can call it whatever they want, just need corresponding pam.conf entries.
The developer has done this but can not get things to work.
Any ideas or help would be greatly appreciated.
Thanks,
Scott