My org is running Active Directory which uses Kerberos for authentication. I have a group of linux computers that are not permitted to be joined to AD. For user authentication, I setup kerberos and pam to point to the AD server. After adding the user to the system, I can login using my AD username and password. After logging in, I have a ticket. This is a great convenience as I don't need to maintain a separate set of credentials for users.
Now I'd like to setup ticket forwarding between my group of computers so I don't have to retype my password every time. This doesnt work.
Example scenario: AD client ssh to server1 in my group of computers not in AD. I can use my username and password to login. After login I have a ticket. I now want to login to server1 in my group of computers not in AD. This prompts me for a password again. Ideally, since I already have a ticket on the AD client, I shouldn't need to enter my password for either login.
Based on my rudimentary understanding of kerberos, I think this is failing on the "TGS-REQ" step where the client tries to get a host (server) service ticket from kdc. Since my host isn't registered/added/joined, I assume the KDC/AD can't provide one and that step fails.
My questions?
- Am I correct, is this the cause of my issues?
- Is there any way around this to achieve my single sign-on using AD creds goal?
- What if I setup my own local KDC/AD/IDM. Is there a way to point that to the main AD?