Unable to Schedule job in SMC after SAS GRID server Authentication changed from SSSD to Winbind

[sagar2]

We changed SAS Grid authentication services from SSSD to Winbind, This was done to overcome SAMBA share enablement of each Node(5).

SAS Version : 9.4 m4

PM version : 9.1

We are able make SAS Grid Application up and authenticated it to Workspace server using AD Credentials.,
Currently issue with we are connecting Flow Manager job scheduler which uses LB passthru to connect Process Platform Manager (PPM) and LSF.
Old scheduled jobs are running fine... But unable to connect and generate new Jobs in application

Below step taken to perform the activity : 

1.Take backup of current config file /etc/sssd/sssd.conf
Stop SSSD
# realm leave
# net ads leave –U administrator
# realm list
# net ads info
# ps aux | grep sssd

2. Configuring Winbind

# net ads join <AD server name> –U administrator
# net ads info
# ps aux | grep winbind
# id <username>

3. Take backup of existing smb.conf & Change id-mapping in smb.conf

Comment below line

idmap config * : backend = tdb

Add below lines

idmap config * : backend = autorid
idmap config * : range = 1368200000-136820000000
idmap config * : rangesize = 2000000
winbind refresh tickets = yes
winbind offline logon = yes
winbind use default domain = yes

# cat /etc/samba/smb.conf | grep -v ^# | grep idmap
# service smb stop; service winbind stop; rm -rf /var/lib/samba/*.tdb /var/log/samba/*; net cache flush; service smb start; service winbind start
# id <username>

4. Changes made in sasauth file as below Link

http://support.sas.com/kb/49/432.html

Error : User are getting below Error and even we are not able to authenticate in flow manager.

Kindly let us know if any steps or configuration need to be done.

Re: Grid deamons @sasadmin1 

[gwootton]

Process Manager uses /etc/pam.d/eauth_userpass PAM configuration to authenticate rather than sasauth. If this isn't linked to the current pam configuration you may need to update it.

https://www.ibm.com/support/pages/account-authentication-process-manager

[sagar2]

created eauth file on Meta and grid master .and added detalsi as mention in steps, 

DO we need to restart the services to take it effect ? i am unable to authenticate yet.

[gwootton]

I believe changes to eauth_userpass would require Process Manager be restarted. I would mention I don't think you would need the things under auth include system-auth.

[sagar2]

 eauth_userpass file was not available , So I generated Manually eauth_userpass file using link Account authentication in Process Manager (ibm.com)

But now when tried to restart jadmin was unable to make :

Even tried stating up Egosh services :

Not sure on how this took place, using Admin /Lsfadmin credential unable to logon to flow manager as well.

[gwootton · Accepted solution]

The link provided is a bit confusing as steps 1 and 2 are the two ways you can create eauth_userpass, so those are either/or not both.

As far as how to start process manager when it's configured as an ego service, as the output mentions this is not done using jadmin but using egosh. The command egosh service list would give you the name of the service and whether or not it is already running. Perhaps ProcessManager instead of processmanager?

If Process Manager is not running I would not expect you to be able to log in to Flow Manager with any user ID.

[sagar2]

Wonderful!! It worked for me :),
It was with name PM in service list.
thanks a lot