Application security roles in an enterprise application are mapped to users, groups, or special subjects, and the special subjects are a convenient way to grant a role to broad categories of caller without naming individuals. The product supplies two principal special subjects: All Authenticated, in the application's realm or in the trusted realms, and Everyone. When the application uses external identity providers, such as when authentication is carried out by a third-party provider through a trust association or by a token from another realm, the callers belong to a realm other than the application's own. The special subject that covers any authenticated user in the trusted realms is "All authenticated in the trusted realm", which is option A.
The application-realm variant, option B, includes only users authenticated in the application's own realm, which would exclude callers who arrive from the external provider. Everyone, option D, grants the role to any caller including unauthenticated ones, which is a much weaker control than the question implies. None, option C, is not a mapping that would grant access.
When mapping roles in the administrative console during installation, or later through the Security role to user/group mapping page, administrators should prefer the narrowest subject that serves the purpose, and test with a user from the external provider to confirm the expected access.
[Reference: Mapping security roles to users and groups; Special subjects (All Authenticated, Everyone); Trusted realms and security domains.]
Submit