Running the web services sample returns “Resource offering not found” (6359900)
Special characters (&) in SAML statements should be encoded (6321128)
Exception occurs when trying to add Disco Service to a role (6313437)
EP Sample does not work if root suffix contains “&” character (6300163)
When Access Manager is configured to access the web services samples under the AccessManager-base/SUNWam/samples/phase2/wsc directory on Solaris systems or the AccessManager-base/identity/samples/phase2/wsc directory on Linux systems, querying the Discovery Service or modifying the Resource Offering returns the error message: “Resource offering not found”.
AccessManager-base is the base installation directory. The default base installation directory is /opt on Solaris systems and /opt/sun on Linux systems.
Workaround:
Go to the following samples directory: AccessManager-base/SUNWam/samples/phase2/wsc) directory on Solaris systems or the AccessManager-base/identity/samples/phase2/wsc directory on Linux systems
In the index.jsp file, search for the following string:
com.sun.org.apache.xml.security.utils.XMLUtils.outputDOM
Immediately before the line that contains the string you found in the previous step, insert the following new line:
com.sun.org.apache.xml.security.Init.init();
Re-run the sample. (You do not need to restart Access Manager.)
If you setup an identity provider (IDP) and a service provider (SP), change the communication protocol to use the browser Artifact profile, and then try to federate users between the IDP and SP, the federation fails.
Workaround: None.
With Access Manager as the source site and destination site and SSO configured, an error occurs in the destination site, because the special character (&) in the SAML statements is not encoded and hence the parsing of assertion fails.
Workaround: None. This problem is fixed in patch 1. See Access Manager 7 2005Q4 Patch 1 for information about applying the patch for your specific platform.
In the Access Manager Console, if you try to add a resource offering to the Disco Service, an unknown exception occurs.
Workaround: None.
Auth Context attributes are not configurable until you have configured and saved other attributes.
Workaround: Configure and save a provider profile before you configure the Auth Context attributes.
If Directory Server has a root suffix that contain the “&” character and you try to add an Employee Profile Service Resource Offering, an exception is thrown.
Workaround: None.
In realm mode, if you federate user accounts on an identity provider (IDP) and service provider (SP), terminate Federation, and then logout, an error occurs: Error: No sub organization found.
Workaround: None.