[ https://issues.jboss.org/browse/ELY-444?page=com.atlassian.jira.plugin.sy... ] David Lloyd updated ELY-444: ---------------------------- Description: When we initially designed the PermissionMapper we went to certain lengths to avoid exposing details of the realm. But now as the API has evolved it is clear that the permission mapper will need access to more information. The AuthorizationIdentity (or perhaps another object which includes the AuthorizationIdentity) should be made available to the permission mapper. In addition, this object could be expanded to include more information about the authentication, for example mechanism-specific information, which can feed into the authorization decision and could be useful for other things. Examples include: authentication timestamp, mechanism name/kind, forwarding credentials, and other attributes which derive from the mechanism as opposed to the identity. was: When we initially designed the PermissionMapper we went to certain lengths to avoid exposing details of the realm. But now as the API has evolved it is clear that the permission mapper will need access to more information. The AuthorizationIdentity should be made available to the permission mapper. In addition, the AuthorizationIdentity could be expanded to include more information about the authentication, for example mechanism-specific information, which can feed into the authorization decision. -- This message was sent by Atlassian JIRA (v6.4.11#64026)