Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
[AS7-6730] Modification to the security interceptors so that the push of the SecurityContext is separated from the authentication step.

Also wrap the Remoting Connection in the Credential so that it can reach the LoginModule instead of relyign on the ThreadLocal, this

means that the Credential will remain available until any intermediate bean sets an alternative.

was: 9f6a8c75700ee942ae622f56dc0c9eff70ae9267

  1. … 1 more file in changeset.
AS7-5114 Fix the EJB JACC workflow.

was: 7edc3b71e22f64debf07f2ce1fc7d4dfc8666a5b

  1. … 1 more file in changeset.
[AS7-4312] Add a registry for the security realms so that they can subsequently be accessed from outside the service dependency mechanisms.

was: 4fe250cfed11a9dcd8a16e0b73c279aa5b75706d

  1. … 2 more files in changeset.
[AS7-4218] When an authentication is handled first using pure SASL we need to make better use of the JAAS based authentication cache - we don't have access to a genuine credential to use in the cache so we use one specific to the connection of the user.

was: 0af6108304784a8b30c1605429a8983b60faf186

    • -0
    • +38
    ./UniqueIdUserInfo.java
  1. … 1 more file in changeset.
[AS7-3525] Don't bring an EJB metadata dependency into the controller module.

was: 194487b8d15a3e5e77740a56020ddb029f350446

  1. … 1 more file in changeset.
[AS7-3525] Update to the JAAS authentication process within the realms to make use of the same security service as used by EJB3.

This change now means that the same authentication cache is used for all JAAS authentication so regardless of the entry point

or the point of the authentication a user will only be authenticated once and the cached value subsequently used whilst the

cache entry is present.

was: 9ec88df402c6a7b09d568159caa0cfc60e675011

    • -0
    • +56
    ./ServerSecurityManager.java
  1. … 3 more files in changeset.
[AS7-1383] Follow on from the current thread association to allow for a SecurityManager to restrict access to update the association.

Also added SecurityAction classes for each location access to the association is needed either to read or to modify.

was: 2fd9700315d1386781fcadfb20a559354814bb62

  1. … 9 more files in changeset.
[AS7-1383] Associate the Subject of the current user with the current request.

was: 6d4f5e29f083f82ab5b24f0e94f6ee65ea858f87

    • -0
    • +48
    ./SecurityContext.java
  1. … 14 more files in changeset.