Fix for OPENAM-6537, review CR-8366 - consider logout logic as not enforced to avoid forcing a user to login when triggering app logout without a session
Reverting initial fix for OPENAM-6537, it didn't take into account the logout parameter property.

Fix for OPENAM-3601, review CR-8422 - Update the JBoss 7 Sample App to make use of more recent EJB3 standards
    • -0
    • +10
    /trunk/openam-agents/jee-agents/pom.xml
  1. … 18 more files in changeset.
Enable installation on Wildvly v8 and v9
Fix for OPENAM-6537, review CR-8366 - treat the value set in the com.sun.identity.agents.config.agent.logout.url property as not-enforced to avoid forcing the user to authenticate before proceeding to the URL if the user does not already have a session
Fix for OPENAM-6615, review via HC - add missing class from whitelst of allowed classes to allow Legacy Password reset option page to function
Fix for OPENAM-5542, review CR-8089 - improve the caching logic of ServiceConfigImpl objects when items are replaced in the cache
Fix for OPENAM-6196, review CR-8146 - review cases where response.getOutputStream() and response.getWriter() were both being called (which is not supported) and make the use of an existing Writer instance more consistent.
Fix for OPENAM-6883, review CR-8238 - Properly handle OpenAM Server URIs that contain a context with mixed case
isNewEntry() is set to true for SMSEntry's that had no attributes or is this the same as not being persisted? I think the less risk approach would be keep this block but follow the same pattern as...

isNewEntry() is set to true for SMSEntry's that had no attributes or is this the same as not being persisted?

I think the less risk approach would be keep this block but follow the same pattern as above, i.e. removing from cache and calling clear() on the result which will provide the same improvement around allowing the collection of ServiceConfigImpl instances.

Don't forget to update the year in header.

Don't forget to update the year in header.

Should this log message also be moved into the new if (profiles) block?

Should this log message also be moved into the new if (profiles) block?

Will correct this date.

Will correct this date.

Remembered overnight that these changes would also impact some JSP pages, updated to include JSPs that needed updating.

Remembered overnight that these changes would also impact some JSP pages, updated to include JSPs that needed updating.

Fix for OPENAM-6196 - don't call getOutputStream() when getWriter() has already been called on the response.
Fix for OPENAM-6196 - don't call getOutputStream() when getWriter() has already been called on the response.
Didn't mean to remove this doc item, have restored.

Didn't mean to remove this doc item, have restored.

Not expecting it to be used in the DAS but if it is then the DAS properties will also need updating.

Not expecting it to be used in the DAS but if it is then the DAS properties will also need updating.

OPENAM-5542 - improve the caching of ServiceConfigImpl instances
OPENAM-5542 - improve the caching of ServiceConfigImpl instances
Fix for OPENAM-6390, review CR-7898 - don't change the case of the returned DN from the getUserDN call
  • More
  • CR-7898
  • summarized and closed
Apart from header, the change has reduced to just: "multipleMatches")); } // single user found.- AMIdentity amId = (AMIdentity)amIdSet.iterator().next(); ...

Apart from header, the change has reduced to just:

                 "multipleMatches"));
         }
         // single user found.
-        AMIdentity amId = (AMIdentity)amIdSet.iterator().next();
+        final AMIdentity amId = (AMIdentity)amIdSet.iterator().next();
+        final String universalId = IdUtils.getUniversalId(amId);
+
         if (debug.messageEnabled()) {
             debug.message("IdRepoDataStoreProvider.getUserID()"
                 + " Name=: " + amId.getName()
                 + " DN=: " + amId.getDN()
-                + " univId=: " + IdUtils.getUniversalId(amId));
+                + " univId=: " + universalId);
         }
-        return DNUtils.normalizeDN(IdUtils.getUniversalId(amId));
+
+        return universalId;
     }
  • More
  • CR-7990
  • summarized and closed
This works fine without the additional DNUtils work.

This works fine without the additional DNUtils work.