Closed sabbyanandan closed 4 years ago
When we moved away from supporting LDAP in favour of just "oauth", opaque token introspection was kinda replacement. It's baked in rather deep in our security classes to map scopes into roles, etc. As Azure AD don't have introspection endpoint, afaik, we'd need to bring back all these ways to handle AD groups.
As a developer, while integrating with Azure AD, I notice the
OpaqueTokenIntrospector
bean is automatically created; however, in Azure AD there's no support for "introspection" endpoint yet, so it needs to be an optional property.OAuthSecurityConfiguration
class creates aOpaqueTokenIntrospector
bean, expecting the following additional configuration to be present:Acceptance:
introspection-uri