OAM R2 Can't Load Client Idp.xml
(Doc ID 1517764.1)
Last updated on JUNE 02, 2014
Applies to:Oracle Access Manager - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
SAML 2.0 IdP metadata fails to load in the OAM console or can be loaded but does not appear after being 'applied'. The following message is logged in the oam-diagnostic.log (in trace mode):
[2012-12-17T15:27:48.609-07:00] [oam_server1] [TRACE:16]  [oracle.oam.diagnostic] [tid: OAM Rate Metric Collection Timer ] [userId: ] [ecid: 54080a57931ad64e:31f208f8:13baaf1fb32:-8000-0000000000000005,0] [SRC_CLASS: oracle.security.am.common.diagnostic.impl.dms.DMSMetricCollectionService] [APP: oam_server#22.214.171.124.0] [SRC_METHOD: calculateRate] Double value expected for collector Collector : OAMS/OAM/OAMController/PreAuthnRequests[[
Type : EVENT
Metrics : 0
LogLevel : INFO
EnableRate : true
EnablePersistence : true
, but found value of type: java.lang.Integer.
An ADF Faces error may be reported in the UI as well when this occurs, depending on the OAM patch level. The same metadata loads successfully in other Federation products (EG, OIF)
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document