Error SMRESTAPI_806 SMRESTAPI 806 in AdminUI when running REST API

Products

• SITEMINDER

Issue/Introduction

 

When running an AdminUI and using REST API code, one might like to
know where to find the description of the returned code.

To illustrate :

  "json": {
  "messages": {
  "Site Minder": "{
  \n \"responseType\": \"error\",
  \n \"status\": 400,
  \n \"data\": [\n {\n \"msgId\": \"SMRESTAPI_806\",\n \"args\": [\n \"[email protected]\"\n ],
  \n \"message\": \"Wrong path for post search: [email protected]\",\n \"code\": 806\n }\n ]\n}"
  },
  "statusCode": "BAD_REQUEST"
  }

Here the return code is 806.

 

Resolution

 

At first glance, the message itself bring the code description as per
above sample, code 806 means

  "Wrong path for post search:
  [email protected]"

This one can occurs if you forget to add the "Domain" in the search
path when creating a "Rule", a "Realm" or a "Policy" like this one for
instance to create a rule (1).

From above sample, {SmDomainName} and {SmRealmName} should be replaced
with a value that exists in the Policy Store. To create an object, you
need to specify parent object and follow the hierarchial url syntax.
   
Here's the full return code list with description for each of them :

  001 : Failed to cleanly stop the serviceInstanceCache.

  002 : The cache is full in spite of removing the LRU entry.  Please
        increase the cache size for better performance.

  003 : Error while trying to authenticate.

  004 : Unable to decrypt the JWT token.

  005 : Error obtaining agent keys.

  006 : Failed to decrypt the JWT auth token with the agent keys.

  007 : Failed to decrypt the JWT auth token with the static agent key.

  008 : Both current key and static key are null.

  009 : No agent keys available to decrypt the JWT auth token.

  010 : Unable to initialize Agent API connection.

  011 : Error processing request: httpcode : {} code : {} message : {}.

  100 : initialization error: {0}

  101 : Invalid class hierarchy: {0}/{1}

  102 : Incorrect Zulu Date Format: {0}

  103 : Incorrect JSON type for {0}: expected {1}, actual {2}.

  201 : POST existing object: {0}

  202 : Wrong xid: {0}

  203 : Invalid class name: {0}

  204 : Inconsistent extension class / base class

  205 : Inconsistent extension class / base class

  206 : Missing extension class

  207 : Missing both xid and actual class

  208 : Unrecognized attribute: {0}

  209 : Inconsistency: {0} exists

  210 : Inconsistency: compound object {0} exists

  211 : Inconsistency: original object {0} exists

  212 : Inconsistency: new object {0} exists

  220 : Operation is not applicable: {0}

  221 : Wrong value for Enumeration {0}: {1}

  222 : Wrong value for Flags {0}: {1}

  301 : Assertion failure in object writer

  401 : Class {0} does not have parent

  402 : {0} unknown operation

  403 : Object not found: {0}

  501 : AddValue: wrong type used while adding value {0}

  601 : Unable to url decode string: {0}

  602 : Invalid search: {0}

  603 : Wrong search path: {0}

  701 : Unable to URLEncode string: {0}

  702 : Failure to add bean: {0}

  801 : Invalid search: {0}

  802 : Wrong path for delete search: {0}

  803 : Attempting to delete nonexistent object: {0}

  804 : Wrong path for put search: {0}

  805 : Attempting to put to nonexistent object: {0}

  806 : Wrong path for post search: {0}

  807 : Class does not exist: {0}

  808 : Object does not exist: {0}

  809 : Bad request. type: {0}

  810 : Bad request. type: {0} mparts: {1}

  811 : Bad request. cannot resolve child class: {0}

  812 : Invalid class name: {0}

  813 : Invalid deployment URL: {0}

  901 : Exception occurred while generating API spec: {0}

  902 : Swagger spec template file not found: {0}

  2320 : IdpLocal validation errors encountered: {0}

  2330 : IdpRemote validation errors encountered: {0}

  2340 : SPLocal validation errors encountered: {0}

  2350 : SPRemote validation errors encountered: {0}

  2355 : Entity validation errors encountered: {0}

  2360 : SPPartnership validation errors encountered: {0}

  2370 : IDPPartnership validation errors encountered: {0}

  2375 : Partnership validation errors encountered: {0}

  2501 : {0} is mandatory

  2502 : Invalid value in {0}

  2503 : Invalid value {0} in {1}. Value must be between {2} and {3}

  2504 : {0} is mandatory when {1} is defined

  2505 : At least one {0} is mandatory for {1}

  2506 : {0} value must be one of {1}

  2507 : At least one of the fields {0} must be {1}

  2508 : Invalid value {0} in {1}. Value must be greater than or equal
         to {2}

  2509 : One of the {0} values must be the default

  2510 : {0} cannot be modified during {1} modification

  2511 : {0} value cannot be empty in {1}

  2512 : Multiple default values are defined for {0}

  2513 : The host defined in Service URL must be a valid sub-domain of
         the Common Domain. See the {0} field value

  2514 : AuthenticantionBaseURL must end with '/Authentication Method
         Group Name'

  2515 : {0} with the name {1} already exists

  2516 : Cannot delete object {0} as the object is referenced by another
         object

  2517 : Invalid value {0} in {1}. Value must be less than or equal to
         {2}

  2518 : Invalid value {0} in {1}. Value must be {2}

  2519 : Invalid value {0} in {1}

  2520 : Invalid certificate {0} for field {1}. Allowed types are {2}

  2521 : Multiple defaults are defined in {0}

  2522 : Invalid URL {0} in {1}

  2523 : Duplicate Index {0} is present for {1}

  2524 : {0} is required for user directory ''{1}''

  2525 : Multiple {0} not allowed for {1}

  2526 : At least one {0} is required.

  2527 : Cannot reach LDAP directory ''{0}'' and determine whether it is
         an Active Directory for handling the correct Group user
         policy. Correct the issue and then create the partnership

  2528 : Dynamic Authentication is not enabled for Authentication
         Context Template ''{0}''

  2529 : Duplicate {0} is present for {1}

  2530 : The protection levels for Authentication Context URI's should
         be in descending order

  2531 : Strength for Authentication Context URI's should be in
         descending order as well as in sequential order

  2532 : First URI strength should be unique and cannot be grouped

  2533 : Not supported Partnership {0} provided. Supported partnership
         objects are IDPPartnership / SAML1xConsToProdPartnership /
         WSFEDRPToIPPartnership / OAuthClientToAuthzServerPship

  2534 : Invalid Redirect URI {0}. Must be a Valid URI

  2535 : {0} cannot be empty or zero

  2536 : {0} value must be greater than {1} value

  2537 : {0} '{1}' contains invalid characters

  2538 : User directory '{0}' of type '{1}' is not supported. The user
         directory type must be AD, LDAP, or ODBC.

  2610 : Partnership {0} is active and cannot be {1}. Deactivate the
         partnership and then try the {2} operation

  2611 : Partnership is already active

  2612 : Remote entity {0} can be used in only one
         partnership. Deactivate partnership {1} or add a disambiguation ID to
         the local entity to make the entity unique

  2613 : Cannot activate partnership as it is not FIPS compliant

  2614 : Partnership {0} is created but activation failed

  2615 : Partnership {0} is created but {1} failed during XPS Service
         call with status code {2}

  2616 : Cannot activate two partnerships with the same Remote Entity
         ID. Deactivate one partnership and then activate the other

  2617 : Remote entity {0} and disambiguation ID {1} can be used in only
         one partnership. Deactivate partnership {2} or change the
         disambiguation ID in the local entity {3} to make the entity unique

  2618 : Partnership is inactive and cannot be deactivated

  2619 : Partnership {0} is saved but deactivation failed

  2620 : Cannot delete Active client configuration: {0}

  2621 : User directory {0} is not attached to {1}, but policy is
         defined

  2622 : Cannot modify entity name(s) during partnership modification

  2623 : Invalid status for partnership {0}

  2624 : Error in fetching certificate information for alias {0}

  2625 : Error in loading certificate into data store for alias {0}

  2626 : An existing certificate entry with the same alias {0} is found

  2627 : An existing duplicate certificate entry is found for alias {0}

  2628 : Certificate {0} expired

  2629 : The Certificate Data Store does not currently support PKCS12
         certificates that contain more than one X509Certificate object

  2630 : The Certificate Data Store does not currently support PKCS12
         certificates that contain more than one RSA private key object

  2631 : Missing either an X509Certificate or a private key. The
         Certificate Data Store supports PKCS12 files that contain at
         least one X509Certificate and RSA private key objects

  2632 : Cannot read X509Certificate data from PKCS12
         certificate. Verify that at least one X509Certificate exists in
         PKCS12 certificate

  2633 : Cannot read private key data from PKCS12 certificate.Verify
         that at least one private key exists in PKCS12 certificate

  2634 : Cannot read RSA private key data from the certificate

  2635 : Only PEM, DER and PKCS12 Certificates are supported

  2636 : The certificate you are trying to import under alias {0} has
         expired and cannot be imported

  2637 : The certificate you are trying to import under alias {0} is not
         yet valid and cannot be imported

  2638 : The certificate being imported already exists in the database
         under a different alias: {0}

  2639 : Update failed. The public key of the new certificate does not
         match the public key for the existing entry under alias

  2640 : Error while updating certificate information: {0}

  2641 : Alias name update for the certificate failed as a certificate
         with the name {0} exists

  2650 : {0} not supported for user directory of type {1}

  2651 : {0} should be selected for all user policies defined for user
         directory {1}

  2700 : Define a password to unwrap private key for loading certificate
         {0}

  2701 : Certificate data update is not permitted on Certificate
         Authority

  2702 : Invalid value in {0}. Values must be one of [KeyEntry,
         Certificate, TrustedCA]

  2703 : PEM/DER format must be used to update TrustedCertificate

  2704 : Invalid update. Multiple PublicKeys in the input matches the
         {0} public key

  2705 : Update failed. The private key in the PKCS12 file does not
         match the private key in the entry selected for update

 

Additional Information

(1)

   Policy Data API - Core Policy Objects

     POST /ca/api/sso/services/policy/v1/SmDomains/{SmDomainName}/SmRealms/{SmRealmName}/SmRules

   https://techdocs.broadcom.com/us/en/symantec-security-software/identity-security/siteminder/12-8/programming/policy-object-rest-apis/rest-api-reference-documentation/policy-data-api-core-policy-objects.html