IDAAS-44008: Unable to instantiate identity provider implementation
Cause: None.
Action: None.
Level: 15
Type: ERROR
Impact: Other
IDAAS-45001: applicationID query parameter is null
Cause: None.
Action: None.
Level: 15
Type: ERROR
Impact: Other
IDAAS-45002: application: {0} : protocol : {1}
Cause: None.
Action: None.
Level: 15
Type: NOTIFICATION
Impact: Other
IDAAS-45003: No identity providers found for application : {0}
Cause: None.
Action: None.
Level: 15
Type: ERROR
Impact: Other
IDAAS-45004: applicationID query param is null
Cause: None.
Action: None.
Level: 15
Type: ERROR
Impact: Other
IDAAS-45005: Exception occurred while retrieving identity providers
Cause: None.
Action: None.
Level: 15
Type: ERROR
Impact: Other
IDAAS-45006: Could not find application : {0}
Cause: Invalid application name specified.
Action: Check application parameter.
Level: 15
Type: ERROR
Impact: Other
IDAAS-45007: Could not authenticate for application : {0} with username : {1}
Cause: Invalid combination of application, username and password (HTTP BASIC).
Action: Check application, username and password.
Level: 15
Type: ERROR
Impact: Other
IDAAS-45008: Mobile application request id parameter is null.
Cause: None.
Action: None.
Level: 15
Type: ERROR
Impact: Other
IDAAS-45009: Mobile application return payload encryption data error.
Cause: None.
Action: None.
Level: 15
Type: ERROR
Impact: Other
IDAAS-45010: Mobile application return url is null.
Cause: None.
Action: None.
Level: 15
Type: ERROR
Impact: Other
IDAAS-45011: Error while redirecting to mobile application return url.
Cause: None.
Action: None.
Level: 15
Type: ERROR
Impact: Other
IDAAS-45012: There is an error while creating JSON response for mobile applications.
Cause: None.
Action: None.
Level: 15
Type: ERROR
Impact: Other
IDAAS-61001: Required Attribute "{0}" is not found in "{1}".
Cause: Displayed when a required attribute in DeviceProfile for Plug-in is missing
Action: None.
Level: 15
Type: TRACE
Impact: Other
IDAAS-61002: Attribute "{0}" in "{1}" should be of type "{2}", instead of "{3}".
Cause: Displayed when an attribute in DeviceProfile for Plug-in is associated with a mismatched type
Action: None.
Level: 15
Type: TRACE
Impact: Other
IDAAS-61003: Hardware Id "{0}" should be of string type.
Cause: Displayed when an attribute in DeviceProfile for Plug-in is associated with a mismatched type
Action: None.
Level: 15
Type: TRACE
Impact: Other
IDAAS-61004: Handle "{0}" should be of string type.
Cause: Displayed when an attribute in DeviceProfile for Plug-in is associated with a mismatched type
Action: None.
Level: 15
Type: TRACE
Impact: Other
IDAAS-61005: "{0}" should be of map / JSON-Object type.
Cause: Displayed when an attribute in DeviceProfile for Plug-in is associated with a mismatched type
Action: None.
Level: 15
Type: TRACE
Impact: Other
IDAAS-61006: Invalid JSON in Multi-Step Authentication Handle.
Cause: Displayed when data stored in OIC Multi-Step Authentication handle contains invalid JSON syntax
Action: None.
Level: 15
Type: TRACE
Impact: Other
IDAAS-61007: Error during sending an email when OTPByEmail Challenge
Cause: Error during sending an email when OTPByEmail Challenge
Action: None.
Level: 15
Type: TRACE
Impact: Other
IDAAS-61008: Invalid geolocation string: {0}
Cause: Invalid geolocation string
Action: None.
Level: 15
Type: TRACE
Impact: Other
IDAAS-61009: The Denied Action is triggered
Cause: The Denied Action is triggered
Action: None.
Level: 15
Type: TRACE
Impact: Other
IDAAS-61010: The Challenge Action is triggered
Cause: The Challenge Action is triggered
Action: None.
Level: 15
Type: TRACE
Impact: Other
IDAAS-61011: The Wipe Out Action is triggered
Cause: The Wipe Out Action is triggered
Action: None.
Level: 15
Type: TRACE
Impact: Other
IDAAS-61012: SMTP Security Type "{0}" is not supported
Cause: SMTP Security Type is not supported
Action: None.
Level: 15
Type: TRACE
Impact: Other
IDAAS-62001: Challenge mechanism has not been set up for user "{0}".
Cause: Displayed by OAAM-OIC Security Plugin when Challenge question is not set up properly for a user
Action: None.
Level: 15
Type: TRACE
Impact: Other
IDAAS-62002: Challenge mechanism has not been set up for user "{0}". Please visit: {1}
Cause: Displayed by OAAM-OIC Security Plugin when Challenge question is not set up properly for a user
Action: None.
Level: 15
Type: TRACE
Impact: Other
IDAAS-62003: What is your OTP Code?
Cause: Displayed question by OAAM-OIC Security Plugin when OTP Challenge
Action: None.
Level: 15
Type: TRACE
Impact: Other
IDAAS-62004: This {0} user id is not known to OAAM server.
Cause: This user id is not known to OAAM Server
Action: None.
Level: 15
Type: TRACE
Impact: Other
IDAAS-62005: Black Listed Mobile Device Rule is triggered
Cause: Black Listed Mobile Device Rule is triggered by OAAM Server
Action: None.
Level: 15
Type: TRACE
Impact: Other
IDAAS-62006: Lost or Stolen Device Rule is triggered
Cause: Lost or Stolen Device Rule is triggered by OAAM Server
Action: None.
Level: 15
Type: TRACE
Impact: Other
IDAAS-62007: This {0} user id is not known to OAAM server. Please visit: {1}
Cause: This user id is not known to OAAM Server
Action: None.
Level: 15
Type: TRACE
Impact: Other
IDAAS-62008: OIC-OTP Code
Cause: OTP Subject when OAAM-OIC Security Plugin is sending an email/SMS for OTP challenge
Action: None.
Level: 15
Type: TRACE
Impact: Other
IDAAS-62009: OIC OTP Code :
Cause: OTP Body Text when OAAM-OIC Security Plugin is sending a SMS/ an Email for OTP challenge
Action: None.
Level: 15
Type: TRACE
Impact: Other
IDAAS-62010: UMS Client Configuration is missing
Cause: UMS Client Configuration is missing
Action: None.
Level: 15
Type: TRACE
Impact: Other
IDAAS-62011: Error During Sending SMS Using UMSClient
Cause: Error During Sending SMS using UMSClient
Action: None.
Level: 15
Type: TRACE
Impact: Other
IDAAS-63001: Mobile SSO Agent credential is missing
Cause: Mobile SSO Agent crediential is missing
Action: None.
Level: 15
Type: TRACE
Impact: Other
IDAAS-63002: Client application identity header refers to a non-agent app: {0}
Cause: Client application identity header refers to a non-agent app
Action: None.
Level: 15
Type: TRACE
Impact: Other
IDAAS-63003: Client application being registered "{0}" participates in SSO, but not an agent app. Hence, it cannot register directly to OIC Server.
Cause: Client application being registered participates in SSO, but not an agent app. Hence, it cannot register directly to OIC Server.
Action: None.
Level: 15
Type: TRACE
Impact: Other
IDAAS-63004: Invalid Credential during Mobile operation
Cause: Generic Invalid Credential
Action: None.
Level: 15
Type: TRACE
Impact: Other
IDAAS-63005: User token is not enough; uid+password is needed for authentication to add a new business app or register a mobile agent app
Cause: user token is not enough; uid+password is needed for authentication to add a new business app or register a mobile agent app
Action: None.
Level: 15
Type: TRACE
Impact: Other
IDAAS-63006: Internet Identity (Relying party for cloud) based User Token is expected.
Cause: Internet Identity (Relying party for cloud) based User Token is expected.
Action: None.
Level: 15
Type: TRACE
Impact: Other
IDAAS-63007: Application {0} cannot be used to register Application {1}, due to SSO Priorities setting
Cause: When Application-X cannot be used to register Application-Y, due to SSO Priorities setting
Action: None.
Level: 15
Type: TRACE
Impact: Other
IDAAS-63008: Client application "{0}" referred in identity header participates in SSO, but it is not an agent app. Hence, it cannot acquire token of {1} type from OIC Server directly.
Cause: Client application referred in identity header participates in SSO, but it is not an agent app. Hence, it cannot acquire (user) token from OIC Server directly.
Action: None.
Level: 15
Type: TRACE
Impact: Other
IDAAS-63009: Missing "clientId" field in Create Client Registration Request
Cause: Missing "clientId" field in Create Client Registration Request
Action: None.
Level: 15
Type: TRACE
Impact: Other
IDAAS-63010: Client application "{0}" does not participate Single-Sign-On. It can register itself directly to OIC Server. It does not need the Client Registration Handle of another app in the HTTP header.
Cause: Client application does not participate Single-Sign-On. It can register itself directly to OIC Server. It does not need the Client Registration Handle of another app in the HTTP header.