you need the necessary keytab files and login.conf,
technically should work, but i haven’t tested this recently, @Anil Sagar @ Google might know the latest on this (for eg, how to access local files might have changed) - this callout uses GSS API, you could actually create your own callout if required
this callout, verifies the incoming kerberos token and generates a new token to talk to the backend. It does not generates Oauth/JWT
Are you trying to do a) kerberos → kerberos or b) OAuth → Kerberos mediation?
If you are trying b)
easiest and recommended approach is to proxy your backend with an IIS and initiate kerberos at the IIS server
I understand this is like an legacy authentication method and many people/accounts would not be interested in but, a 4MV4D video series on this topic would be great @Anil Sagar @ Google
Thanks Anil. Actually I have placed the configuration places under opt\apigee folder directly. so do I need to place the files under /opt/apigee/edge-message-processor? or /opt/apigee/edge-message-processor/bin?
What is the recommended model for supporting 3rd party plugin to enable Kerberos Constrained Delegation? I see that there is no built-in support for Kerberos and probably need to rely on 3rd party plugin? How do we verify if the plugin is secure, not prone to security vulnerabilities?
,
Does APIGEE provide support in case if the custom kerberos modules to enable constrained delegation does not work? Please let me know.