2 people found this helpful
So I just looked through the code base and I do not see support for the /introspect end-point or logic. The only way to do this (to my knowledge), would to be put a middleware service in front of Jive to proxy the requests...and implement the /introspect end-point as a proxy call to /api/core/v3/people/@me or some other similar call ... and construct the payload based on the status code being != 401. =\
Oddly enough Jive supports Open ID as an identity provider, but that seems to be more of Jive as a consumer, rather than a producer in the flow.
While not the perfect answer, until this feature is requested (and I've logged it internally in our backlog) by customers as a gap...it wont get much traction. So definitely file a support ticket and reference:
CUSTOM-3323 and CLOUD-5472
Hope that helps.