For a number of years we have been happily using Kerberos Transparent Auth SSO. We have multiple domains around the world.
This continues to work fine for existing gateways. We use the identity agent and with browser based sso as a backup.
So each domain would have the SPN for the gateway and the ckp_pdp registered. Has worked fine - for years.
The problem we have regards new gateways that we want to have registered in AD. Previously in a server 2008 AD environment you could have duplicate SPN's in a forest - ie so each domain can have the new firewall registered.
On server 2012 AD controllers the use of SPN -a has been depreciated and the SPN has to be unique in the forest. This means that we cannot register the new gateway in each domain.
Has anyone else encountered this - we want to stick with the identity agent, and no identity collectors or AD query.
How did you address this situation. It has only recently been an issue as we have a couple of new gateways and the last of the old 2008 AD controllers have now gone.
Thanks