I'm unaware of any specific limitation around using OAuth and Kerberos together. For your reference, please also see:
Due to the complexity of Kerberos, this setup works only on-premise and requires a Jive Professional Services (PS) engagement. For your customer configuration, did you work with our PS team, or did you develop this yourself?
- If this was developed by PS, I would recommend submitting a support case in your private Jive Community customer group for troubleshooting assistance.
- If you developed this yourself as a customization, then this is likely outside the scope of Jive Customer Support, so I would recommend moving the question to the Jive Developers space for input from the development community.
I hope this helps. Let me know if you had any other questions on this.