Authorisation determines what an authenticated identity is permitted to do, and WebSphere Application Server supports several technologies that decide this. The product's security documentation identifies them as the Java Message Service security model, which applies authorisation to messaging resources such as destinations, and the Java Authorization Contract for Containers, JACC. JACC defines how the application server hands authorisation decisions to a provider, so an external authorisation system such as Tivoli Access Manager can control access to Java EE resources. Options B and D are the two that fit.
The other items relate to authentication and identity federation, not authorisation. OAuth is a protocol for delegated authorisation to third-party clients, and OpenID Connect builds an identity layer on top of OAuth 2.0, so both appear in the product as token-based mechanisms that provide trust and identity rather than as the authorisation technologies in the product's list. The Security Assertion Markup Language, SAML, is an assertion format used for single sign-on and federated authentication.
The distinction matters in practice. Authentication, whether through LTPA, SPNEGO, OpenID Connect, or SAML, establishes who the caller is, while authorisation, through the Java EE role model and JACC or the JMS controls, establishes the resources that caller may reach. Administrators should configure and test each layer separately.
[Reference: Authorization technology; Java Authorization Contract for Containers (JACC); Service integration security and JMS; Administrative and application security.]