Kony Error Codes · ComponentsErrorCodes Version1.0 RevisionHistory Date DocumentVersion...

Kony Fabric

Components Error Codes

Release V8

Document Relevance and Accuracy

This document is considered relevant to the Release stated on this title page and the document version stated on the Revision History page.

Remember to always view and download the latest document version relevant to the software release you are using.

© 2017 by Kony, Inc. All rights reserved 1 of 79

Components Error CodesVersion1.0

Copyright © 2017 Kony, Inc.

All rights reserved.

September, 2017

This document contains information proprietary to Kony, Inc., is bound by the Kony license

agreements, and may not be used except in the context of understanding the use and methods of

Kony, Inc., software without prior, express, written permission. Kony, Empowering Everywhere, Kony

Fabric, Kony Nitro, and Kony Visualizer are trademarks of Kony, Inc. MobileFabric is a registered

trademark of Kony, Inc. Microsoft, theMicrosoft logo, Internet Explorer, Windows, andWindows Vista

are registered trademarks of Microsoft Corporation. Apple, the Apple logo, iTunes, iPhone, iPad, OS

X, Objective-C, Safari, Apple Pay, Apple Watch, and Xcode are trademarks or registered trademarks

of Apple, Inc. Google, the Google logo, Android, and the Android logo are registered trademarks of

Google, Inc. Chrome is a trademark of Google, Inc. BlackBerry, PlayBook, Research in Motion, and

RIM are registered trademarks of BlackBerry. SAP® and SAP® Business Suite® are registered

trademarks of SAP SE in Germany and in several other countries. All other terms, trademarks, or

service marks mentioned in this document have been capitalized and are to be considered the

property of their respective owners.



Revision History

Date Document Version Description of Modifications/Release

09/19/2017 1.0 Document published for V8GA



Table of Contents

1. Kony Integration Service Error Codes 5

2. Kony Identity Service Error Codes 37


1. Kony Integration Service Error Codes Components Error CodesVersion1.0

1. Kony Integration Service Error Codes

The following are the error codes for Kony Integration Services. Each error code table consists of the

error message, description of the error, severity, way to reproduce the error, error resolution and point

of contact.

Error 1528

MESSAGE One ormore of the services failed in the composite service.

DESCRIPTION This means that one of the services executed as part of the

composite service has failed. The actual error code and

message can be found in the logs for the individual services.

SEVERITY HIGH

REPRODUCE THE ERROR Provide invalid service URL for one of the services.

RESOLUTION Resolve the issue faced by the individual service which

depends on the error code provided by that service.

POINT OF CONTACT Depends on the error code for the individual services.

Error 5000

MESSAGE Controller Initialization Error.

DESCRIPTION This means that the initialization of the ControllerDef.xml file

was improper.

SEVERITY LOW



Error 5000

REPRODUCE THE ERROR Create improper XML tags in the ControllerDef.xml file.

Restart the server. While loading the controller

configurations, this error is thrown.

RESOLUTION Please check the ControllerDef.xml file.

POINT OF CONTACT KONY

Error 5001

MESSAGE Mandatory Request parameter channel is missing.

DESCRIPTION Kony Server is being hit from places other than the device.

Mandatory parameter channel is missing

SEVERITY SEVERE

REPRODUCE THE ERROR Remove the request parameter "channel" while invoking the

Kony Server.

RESOLUTION Check the request parameters for mandatory parameter:

channel.


Error 5002

MESSAGE Mandatory Request parameters - appID, serviceID or both

aremissing.



Error 5002

DESCRIPTION Kony Server is being hit from places other than the device. All

themandatory parameters such as- appID, serviceID or both

aremissing.

SEVERITY SEVERE

REPRODUCE THE ERROR Remove the request parameter appID or serviceID while

invoking the Kony Server.

RESOLUTION Check the request parameters for mandatory parameter :

appID and serviceID.


Error 5004

MESSAGE Processor definition does not exit.

DESCRIPTION This means that the processor classes (DataChunking,

ImageProcessor, ServiceDelegate and so on) are not present

in the ControllerDef.xml file. This may lead to loss of

functionality. Possible tampering.

SEVERITY HIGH

REPRODUCE THE ERROR Remove the <ProcessorConfiguration> with attribute name

"ServiceDelegator" from the ControllerDef.xml file.

RESOLUTION Check controllerDef.xml for the processor being invoked and

check if it is present and correct.




Error 5005

MESSAGE Cannot load the processor class.


ImageProcessor, ServiceDelegate and so on) present in the

ControllerDef.xml file could not be loaded by the JVM. This

may lead to loss of functionality. Possible tampering. Check

availability of the classes.

SEVERITY HIGH

REPRODUCE THE ERROR Modify the <ProcessorConfiguration> tag with attribute name

"ServiceDelegator" and change the classname to "abc.xyz".

Since this class is not present, it throws up this error.

RESOLUTION Check if themiddleware-system.jar is present and the

processor class is present in that jar. Also, check if no other

jar file contains the same class name as this processor class.


Error 5006

MESSAGE Invalid JSON response for the service.


ImageProcessor, ServiceDelegate and so on) present in the

ControllerDef.xml file could not be instantiated by the JVM.

This may lead to loss of functionality. Possible tampering.

SEVERITY HIGH



Error 5006

REPRODUCE THE ERROR Modify the <ProcessorConfiguration> tag with attribute name

"ServiceDelegator" and change the classname to "abc.xyz"

where abc.xyz is an interface/abstract class. Since this an

interface, it throws up this error.

RESOLUTION Check if themiddleware-system.jar is present and the

processor class is present in that jar. Also, check if the

processor class being invoked is not an interface/abstract

class.


Error 5101

MESSAGE Sequence definition does not exit.

DESCRIPTION This means that the sequence of processors (as described

above) are not present for that particular channel (Native

Apps, MobileWeb etc). This should be present in the

ControllerDef.xml file. This may lead to loss of functionality.

Possible tampering.

SEVERITY HIGH

REPRODUCE THE ERROR Remove the <SequenceConfiguration> with attribute name

"default" from the ControllerDef.xml file.

RESOLUTION Check if the required sequence is present and correctly

defined in the controllerDef.xml.




Error 5101

MESSAGE Problem in Creating / Loading the sequence class.

DESCRIPTION This means that the sequence of processors (as described

above) could not be loaded for that particular channel (Native

Apps, MobileWeb and so on). Check ControllerDef.xml file

for the sequence. Check availability of the classes defined.

This may lead to loss of functionality. Possible tampering.

SEVERITY HIGH

REPRODUCE THE ERROR Modify the <SequenceConfiguration> tag with attribute name

"default" and change the classname to "abc.xyz". Since this

class is not present, it throws up this error.

RESOLUTION Check if the sequence class being invoked is present in the

middleware-system.jar. Check if no other jar file contains the

same class name as this processor class. Also, check if

there has been no IllegalAccessError while instantiating the

class.


Error 6000

MESSAGE Session does not exist.

DESCRIPTION Session does not exist.

SEVERITY MEDIUM

REPRODUCE THE ERROR Set the session object to null in the pre-processor.

RESOLUTION Check the pre-processor.



Error 6000


Error 6001

MESSAGE Session exists (may be newly created) but there are no

expected values.

DESCRIPTION The session exists but the value in the session is null.

SEVERITY MEDIUM

REPRODUCE THE ERROR In the service-definition file, change the scope of an input

variable to session and do not save this value in session in

the pre-processor or any previous service.

RESOLUTION Ensure that the value being looked for is present in the

session. Check the service-definition file for the particular

service and check if the scope of the concerned input variable

is correct (It can be session/request).


Error 8004

MESSAGE Operation invocation problem.

DESCRIPTION Unable to invoke themethod on pre/post processors or the

Java services.

SEVERITY HIGH



Error 8004

REPRODUCE THE ERROR Remove the application jar from the application server

libraries.

RESOLUTION Check if the latest application jar is present. Also, check if

there is no class conflict in the logs.


Error 8005

MESSAGE Response is empty.

DESCRIPTION Backend service is returning empty response.

SEVERITY HIGH

REPRODUCE THE ERROR Re-direct the service call to a dummy server which returns an

empty response.

RESOLUTION Check the back-end services if they are up. Check

connectivity with the back-end servers.

POINT OF CONTACT Back-end service provider.

Error 8006

MESSAGE Invalid XMLResponse.

DESCRIPTION Check response from back-end server.

SEVERITY HIGH



Error 8006

REPRODUCE THE ERROR Create a dummy service on the back-end server to return a

HTTP Response with error codes such as 401/500, it throws

up this error.

RESOLUTION Check response string from back-end servers. A common

scenario would be when the back-end server returns an

HTTP Response (401/500) for an XML/Soap request. This is

treated as invalid by Kony Server. Please check if the

response from the back-end server is a valid XML or Soap

request.


Error 8007

MESSAGE Error parsing the XML response.

DESCRIPTION This error is returned if the Kony Server could not parse the

XMLwith the given XPath.

SEVERITY HIGH

REPRODUCE THE ERROR Provide incorrect XPath to parse the XML response.

RESOLUTION Check if the XPathmatches the XML response returned by

the service.




Error 8008

MESSAGE Invalid Result object returned onmethod invocation.

DESCRIPTION The object returned after invoking the pre/post processor or

the Java service does not cast to

com.konylabs.middleware.dataobject.Result object.

SEVERITY HIGH

REPRODUCE THE ERROR Modify the processor such that it does not return valid Result

object.

RESOLUTION Ensure if proper application jar is present and is returning

proper object. Also, check if there is no class conflict in the

logs.


Error 8009

MESSAGE Request unsuccessful, server responded with status code

xxx.

DESCRIPTION If the received status code is not 200, Kony Server throws

this error.

SEVERITY HIGH

REPRODUCE THE ERROR Shutdown the service so that a 404 or 500 error is thrown by

the server hosting the service. Try to access the service

through Kony Server and the error is reproduced.

RESOLUTION Check if the services are accessible.



Error 8009


Error 8010

MESSAGE Operation invocation problem.

DESCRIPTION Unable to invoke themethod Scraper services.

SEVERITY HIGH

REPRODUCE THE ERROR Remove the scraper.jar from the application server libraries.

RESOLUTION Check if the latest scraper.jar is present. Also, check if there

is no class conflict in the logs.


Error 8013

MESSAGE Cannot get value for the expression.

DESCRIPTION The tag is empty for the particular xpath in the response.

SEVERITY LOW

REPRODUCE THE ERROR Create a service-output parameter which is not present in the

response for that particular service.



Error 8013

RESOLUTION Check the XML response and the service-definition file to

ensure that the tag being parsed for is present in the

response. Modify the service-definition file if this is not the

case.


Error 8018

MESSAGE Unable to create object for class <NameOfTheClass>

DESCRIPTION Unable to invoke the pre/post processors or the Java

services.

SEVERITY LOW

REPRODUCE THE ERROR Remove the application jar from the application server

libraries.

RESOLUTION Check if the application jar is present. Also, check if there is

no class conflict in the logs.


Error 8701

MESSAGE Invalid source to the parameter for<user input text>.

DESCRIPTION Incorrect scope (value of 'src') is used for parameters values.

SEVERITY LOW



Error 8701

REPRODUCE THE ERROR Provide value other than 'request' or 'session'.

RESOLUTION Parameter sourcemust be either of 'request', or 'session'.


Error 8702

MESSAGE Request failed with exception:<ExceptionMessage>.

DESCRIPTION Exception has occurred while requesting SAP service.

SEVERITY HIGH

REPRODUCE THE ERROR NA

RESOLUTION NA


Error 8703

MESSAGE Request failed with JCO exception:<ExceptionMessage>.


SEVERITY HIGH


RESOLUTION NA



Error 8703


Error 8704

MESSAGE Request failed with ABAP exception:<ExceptionMessage>.


SEVERITY HIGH


RESOLUTION NA


Error 8710

MESSAGE Provide the properties file for connection information.

DESCRIPTION SAP properties file (sap_<servername>.properties) config

parameter is missing in the service definition.

SEVERITY MEDIUM

REPRODUCE THE ERROR When service does not have properties file in service

definition.

RESOLUTION SAP properties file must be provided in the service definition,

using 'sapserverfile' config parameter.




Error 8711

MESSAGE Provide 'username' as a request parameter.

DESCRIPTION 'username' is missing from the request parameters.

SEVERITY LOW

REPRODUCE THE ERROR Do not provide username in the service request.

RESOLUTION Supply the 'username' via request parameter.


Error 8712

MESSAGE Provide 'password' as a request parameter.

DESCRIPTION 'password' is missing from the request parameters.

SEVERITY LOW

REPRODUCE THE ERROR Do not provide password in the service request.

RESOLUTION Supply the 'password' via request parameter.


Error 8713

MESSAGE SAP properties not loaded at server load

(SAPConnectorListner in web.xml needs to be enabled).



Error 8713

DESCRIPTION SAP properties files are not loaded at server start.

SEVERITY LOW

REPRODUCE THE ERROR Do not register SAPConnectorListener in web.xml.

RESOLUTION Register SAPConnectorListner in web.xml.


Error 8714

MESSAGE Error parsing input parameters.

DESCRIPTION Could not parse the input JSON data supplied.

SEVERITY MEDIUM

REPRODUCE THE ERROR Provide invalid JSON data in the service request.

RESOLUTION Validate the input data JSON format.


Error 8801

MESSAGE Siebel sessionid is empty, login again.

DESCRIPTION Siebel session is empty in the request.

SEVERITY LOW



Error 8801

REPRODUCE THE ERROR Do not provide session ID value.

RESOLUTION First request the 'login' service which returns the session ID.

Pass this session ID in the subsequent service requests.


Error 8802

MESSAGE Unsupported Siebel operation - opcode: <opcode value>.

DESCRIPTION Invalid Siebel operation opcode in the request.

SEVERITY LOW

REPRODUCE THE ERROR When opcode does not match valid ones.

RESOLUTION Siebel service 'opcode' mentioned in the service def is not

valid. It has to be either of login, logout, create, update,

delete, query, service.


Error 8803

MESSAGE Siebel exception while performing operation= <operation>

DESCRIPTION Siebel exception has occurred.

SEVERITY HIGH



Error 8803


RESOLUTION NA


Error 8804

MESSAGE Invalid connection URL or username or password.

DESCRIPTION Invalid URL/username/password for Siebel service.

SEVERITY LOW

REPRODUCE THE ERROR Provide incorrect URL/username/password.

RESOLUTION Provide correct URL, username, password.


Error 8805

MESSAGE Invalid source type for service.

DESCRIPTION Session ID is not valid or expired.

SEVERITY LOW

REPRODUCE THE ERROR Provide invalid session ID.

RESOLUTION Request login service and use the new session ID.



Error 8805


Error 8806

MESSAGE Invalid source type for service.

DESCRIPTION Trying to update/insert multi valued field with single value.

SEVERITY LOW

REPRODUCE THE ERROR Provide single value for multi valued field.

RESOLUTION Providemulti valued data.


Error 8807

MESSAGE Servicemethod not found or more than one found in specified

service: <Method Name> in<Service Name>.

DESCRIPTION Specified Siebel service is not found.

SEVERITY LOW

REPRODUCE THE ERROR Request a Siebel service which does not exist.

RESOLUTION Verify the Siebel service name.




Error 8901

MESSAGE JMS opcode/propertiesfile/mqconfig cannot be empty.

DESCRIPTION JMS opcode, propertiesfile, mqconfig config parameters are

missing from service definition.

SEVERITY LOW

REPRODUCE THE ERROR When opcode/propertiesfile/mqconig config parameters are

missing from service definition.

RESOLUTION Provide correct opcode, properties file, mqconfig config

parameters in service definition.


Error 8902

MESSAGE Invalid JMS opcode: <JMS opcode value>.

DESCRIPTION Invalid opcode is used.

SEVERITY LOW

REPRODUCE THE ERROR Use opcode other than valid ones.

RESOLUTION Use correct opcode (either of 'send', 'receive', 'send_

receive').




Error 8903

MESSAGE Properties not loaded at server start: <properties file name>.

DESCRIPTION Invalid opcode used

SEVERITY LOW

REPRODUCE THE ERROR Do not register JmsConnectorListener in web.xml.

RESOLUTION Register JmsConnectorListener in web.xml.


Error 8904

MESSAGE Invalid MQ config name: <MQConfig name>

DESCRIPTION mqconfg name not found in the properties file defined for the

service.

SEVERITY MEDIUM

REPRODUCE THE ERROR Do not providemqconfig config parameter in service

definition.

RESOLUTION Use correct mqconfig.


Error 8905

MESSAGE Exception while getting objects from DS.



Error 8905

DESCRIPTION Exception occurred while gettingmanaged JMS objects from

directory server.

SEVERITY MEDIUM


RESOLUTION NA


Error 8906

MESSAGE Exception while creatingWMQobjects.

DESCRIPTION Exception occurred while creating non-managed JMS

connection.

SEVERITY MEDIUM


RESOLUTION NA


Error 8907

MESSAGE JMS connector exception: opcode= <JMS opcode value>

DESCRIPTION Exception occurred while performing JMS operation.



Error 8907

SEVERITY HIGH


RESOLUTION NA


Error 8908

MESSAGE Failed to sendmessage to: <ExceptionMessage>.

DESCRIPTION Failed to sendmessage tomentioned queue/topic.

SEVERITY MEDIUM


RESOLUTION NA


Error 8908

MESSAGE Failed to sendmessage to: <Queue/Topic name>.

DESCRIPTION Failed to sendmessage tomentioned queue/topic.

SEVERITY MEDIUM




Error 8908

RESOLUTION NA


Error 8909

MESSAGE MQ internal error: message sent, but could not get message

ID.

DESCRIPTION Message sent, but message ID is not received fromMQ

server.

SEVERITY HIGH

REPRODUCE THE ERROR WebsphereMQ bug

RESOLUTION Probably aMQ bug


Error 8910

MESSAGE JMS StreamMessage type is not handled yet.

DESCRIPTION Not implemented

SEVERITY LOW

REPRODUCE THE ERROR Whenmessage is a Streammessage.

RESOLUTION NA



Error 8910


Error 8910

MESSAGE JMS ObjectMessage type is not handled yet.


SEVERITY LOW

REPRODUCE THE ERROR Whenmessage is Object message.

RESOLUTION NA


Error 8910

MESSAGE JMS ByteMessage type is not handled yet.


SEVERITY LOW

REPRODUCE THE ERROR Whenmessage is Bytemessage.

RESOLUTION NA




Error 9001

MESSAGE IOExceptions

DESCRIPTION Caused due to read time-outs or due to inability to open a

connection.

SEVERITY HIGH

REPRODUCE THE ERROR Create a dummy service on the back-end server to return a

response with aMalformedURL exception. This can be done

by returning a response with an invalid charset encoding.

RESOLUTION Check the connectivity to back-end server and check if the

response from the back-end server is correct.


Error 9105

MESSAGE Unable to fill message template.

DESCRIPTION This error is thrownwhen the Kony Server is unable to create

the request XML/Soapmessage from the input parameters in

the request/session.

SEVERITY HIGH

REPRODUCE THE ERROR Pass a dataset as the input variable in the pre-processor for a

particular service while keeping the attribute "datatype" of the

input variable in the service-definition file as "String".

RESOLUTION Check the input variables and their datatype. Also, check if

the datatype of the input variable is the same as specified in

the service-definition file.



Error 9105


Error 9109

MESSAGE Unable to open connection to endpoint URL / Unable to open

connection for the given service.

DESCRIPTION This error is returned to the device in the event of any

exception occurring while connecting and invoking the back-

end service through connectors like XML/Soap. Look at the

log file for related java stack traces. This error could also

appear due to the failure of HTTP client init due to

misconfiguration or missing license related values in the

middleware.properties file.

SEVERITY LOW

REPRODUCE THE ERROR One of the ways to create this error is to specify an invalid

classname "abc.xyz" as the pre-processor for a particular

service in the service-definition file and invoke that service.

Since this class is not present, this error will be thrown. You

could also reproduce this error by removing the SMTP

configuration from themiddleware.properties file.

RESOLUTION Check themiddleware.log for previous java exceptions and

stack-traces. Check themiddleware.properties configuration

values as mentioned in the Kony Sever installation guide.




Error 10101

MESSAGE Application does not exist with the AppID.

DESCRIPTION The service definition file has beenmoved/renamed from it's

original location.

SEVERITY SEVERE

REPRODUCE THE ERROR In the service-definition file, change the attribute "id" of the

tag <application> to "xyz" and restart the server. Since the

application ID is no longer present, this error is thrown.

RESOLUTION The service definition file has beenmoved/renamed from it's

original location. Check theMIDDLEWARE_

HOME/middleware/ middleware-bootconfig/appregistry/

folder to check if the required service-definition file is present

and valid. Re-generate the service.


Error 10102

MESSAGE Service does not exist with the ServiceID.

DESCRIPTION Kony Server is being hit with an invalid service ID. Possible

hack.

SEVERITY SEVERE

REPRODUCE THE ERROR Invoke themiddleware application by giving the request

parameter serviceID=xyz. Since this serviceID is not present

in the service-definition file, this error is thrown. Alternatively,

change the service-definition file by changing the attribute

name.



Error 10102

RESOLUTION Check the service-definition file for the particular service

being invoked. The <service> tag for that service should be

present and should be defined correctly.


Error 10103

MESSAGE Unsupported service type.

DESCRIPTION Service definition file has been tampered with. Check the

type of the service as defined in the service definition.

SEVERITY HIGH

REPRODUCE THE ERROR Change the service-definition file by changing the attribute

"type" of a particular service to "abc.xyz". Restart the server.

Invoke the service. Since this type is not defined in the

ControllerDef.xml file, this error is thrown.

RESOLUTION Check the service-definition file for the particular service

being invoked. Check the attribute "type" in the service tag.

This attribute should be present under the

<ProcessorConfiguration> tag in ControllerDef.xml file along

with the appropriate fully qualified class name.


Error 10104

MESSAGE Cannot load a Connector.



Error 10104

DESCRIPTION Unable to find the class pertaining to the connector specified

in the service definition file and ControllerDef.xml file.

ClassNotFoundException. Possible tampering of service

definition file/libraries.

SEVERITY HIGH

REPRODUCE THE ERROR Change the ControllerDef.xml file by changing the <Config>

tag under <ProcessorConfiguration>. Change the attribute

"value" for any of the connectors to "abc.xyz". Restart the

server. Invoke the service which is of this type. Since the

class abc.xyz is not present, this error is invoked.

RESOLUTION Check the ControllerDef.xml file for fully qualified class name

of the particular connector. Also, check if the class is present

in the classpath.


Error 10105

MESSAGE Cannot instantiate a Connector.

DESCRIPTION Unable to instantiate the class pertaining to the connector

specified in the service definition file and ControllerDef.xml

file. InstantiationException. Possible tampering of service

definition file/libraries.

SEVERITY HIGH



Error 10105

REPRODUCE THE ERROR Change the ControllerDef.xml file by changing the <Config>

tag under <ProcessorConfiguration>. Change the attribute

"value" for any of the connectors to "abc.xyz" where abc.xyz

is an interface/abstract class. Restart the server. Invoke the

service which uses that particular connector. This error is

thrown.

RESOLUTION Check the ControllerDef.xml file for fully qualified class name

of the particular connector. Also, check if the class is present

in the classpath and it is not an interface or an abstract class.


Error 12001

MESSAGE Unable to connect to device database.

DESCRIPTION Connection to the device database is lost. Resolve

immediately.

SEVERITY SEVERE

REPRODUCE THE ERROR Bring down the database server. Invoke any service and this

error is thrown.

RESOLUTION Check connection to the database server. Check the context

specified. Check the credentials of the database server and,

if Kony Server has permissions to access the database.




Error 12003

MESSAGE Error while executing Select Queries.

DESCRIPTION Check the query andmanually query the database with the

same. Possible tampering with the database tables and/or

data.

SEVERITY HIGH

REPRODUCE THE ERROR Modify the database and change the name of table

"konylogdb.devicemaster" to "konylogdb.devmaster". Since

the Kony Server queries the devicemaster table, this error is

thrown.

RESOLUTION Check the query andmanually query the database with the

same. Possible tampering with the database tables and/or

data.



2. Kony Identity Service Error Codes Components Error CodesVersion1.0

2. Kony Identity Service Error Codes

The following are the error codes for Kony Identity services. Each error code table consists of the error

message, description of the error, severity, way to reproduce the error, error resolution and point of

contact.

-1: FAILURE_UNCATEGORIZED

MESSAGE Uncategorized Failure

DESCRIPTION The error/failure is not available in the error/failure list

SEVERITY HIGH


RESOLUTION Review the scenario and verify all the details


-2: FAILURE_INVALID_TENANT

MESSAGE Invalid Auth Service Tenant

DESCRIPTION The tenant information is wrong.

SEVERITY HIGH

REPRODUCE THE ERROR The exception occurs when other internal components (like

middleware, portal etc.) try to communicate with Auth that

provides wrong tenant details.

RESOLUTION Verify environment configurations



-2: FAILURE_INVALID_TENANT

POINT OF CONTACT NA

-3: FAILURE_INVALID_CREDENTIALS

MESSAGE Invalid User/App Credentials

DESCRIPTION The error is thrownwhen the username/password or app

key/secret provided is wrong.

SEVERITY LOW

REPRODUCE THE ERROR Provide invalid username/password or app key/secret

RESOLUTION Provide valid username/password or app key/secret

POINT OF CONTACT NA

-4: FAILURE_INVALID_USER_CREDENTIALS

MESSAGE Invalid User Credentials

DESCRIPTION The error is thrownwhen the user name or password provided

is wrong

SEVERITY LOW

REPRODUCE THE ERROR Provide invalid credentials

RESOLUTION Provide valid credentials

POINT OF CONTACT NA



-5: FAILURE_INVALID_TOKEN

MESSAGE Token invalid

DESCRIPTION Wrong token is passed while invoking a service

SEVERITY MEDIUM

REPRODUCE THE ERROR Invoke a service with wrong token

RESOLUTION Use valid token

POINT OF CONTACT NA

-6: FAILURE_EXPIRED_TOKEN

MESSAGE Token expired

DESCRIPTION Expired token is passed while invoking Auth service

SEVERITY LOW

REPRODUCE THE ERROR Invoke service with expired token

RESOLUTION Use non-expired token

POINT OF CONTACT NA

-7: FAILURE_INVALID_PROVIDER

MESSAGE Invalid Provider



-7: FAILURE_INVALID_PROVIDER

DESCRIPTION The exception occurs when a wrong Provider name is

specified in Login Request

SEVERITY LOW

REPRODUCE THE ERROR Specify wrong Provider name in Log-in Request

RESOLUTION Enter a valid Provider name

POINT OF CONTACT NA

-8: FAILURE_USER_NOT_ACTIVE

MESSAGE This User is currently inactive

DESCRIPTION The exception Occurs when log-in request is made with a

user who is inactive

SEVERITY LOW

REPRODUCE THE ERROR Make log-in request with inactive user

RESOLUTION Convert user to active or try login with active user

POINT OF CONTACT NA

-9: FAILURE_INVALID_APP_CREDENTIALS

MESSAGE Invalid App Credentials



-9: FAILURE_INVALID_APP_CREDENTIALS

DESCRIPTION The exception occurs when a user tries to fetch applications

by providing wrong details (App key or App secret or App Id)

SEVERITY LOW

REPRODUCE THE ERROR Fetch applications by providing wrong details (App key or App

secret or App Id)

RESOLUTION Verify App key (or) App secret (or) App Id used in fetching

applications

POINT OF CONTACT NA

-12: FAILURE_UNSUPPORTED

MESSAGE Unsupported Operation

DESCRIPTION The exception occurs when a user:

l Attempts to refresh back end token but provider does

not allow it

l Attempts decoding the install info of JWT On-premise

l Attempts to create license info for JWT api On-

premise

l Requests unsupported operation on License.

(Supported operations: activate, check and update)

l Attempts to exchange license claims on cloud

SEVERITY HIGH



-12: FAILURE_UNSUPPORTED

REPRODUCE THE ERROR l Try to refresh backend token

l Try to decode install info of JWT On-premise

l Try to create a license info for JWT api On-premise

l Request unsupported operation on License.

l Try to exchange license claims on cloud.

RESOLUTION Stop requesting above unsupported operations

POINT OF CONTACT NA

-13: FAILURE_INVALID_GRANT_TYPE

MESSAGE Invalid Grant Type

DESCRIPTION The exception occurs when a user attempts to authenticate

by providing invalid grant type.

SEVERITY HIGH

REPRODUCE THE ERROR Attempt to authenticate by providing invalid grant type

RESOLUTION Provide valid grant type (CLIENT_CREDENTIALS/

EXTENSION/ PASSWORD)


-14: FAILURE_EXTERNAL_IDP

MESSAGE Configured IdP Service Unavailable



-14: FAILURE_EXTERNAL_IDP

DESCRIPTION The exception occurs when an application fails to fetch the

user profile from OAuth2 backend.

SEVERITY HIGH

REPRODUCE THE ERROR Fetch user profile data using invalid token.

RESOLUTION Use valid token to fetch user profile from OAuth2 backend

POINT OF CONTACT NA

-15: FAILURE_NO_SYSTEM_CLAIMS

MESSAGE Error Reading System Claims

DESCRIPTION The exception occurs when null Access control information is

received after exchanging OrgAuth or LicenseAuth claims

SEVERITY HIGH

REPRODUCE THE ERROR Exchange a claim which gives null Access control

information

RESOLUTION Exchange a proper claim

POINT OF CONTACT NA

-17: FAILURE_INVALID_OPERATION

MESSAGE Invalid Operation



-17: FAILURE_INVALID_OPERATION

DESCRIPTION The exception occurs while exchanging rolens for

accounts.auth tenant

SEVERITY HIGH


RESOLUTION NA


-18: FAILURE_USER_NOT_AUTHORIZED_FOR_TENANT

MESSAGE User not authorized for tenant

DESCRIPTION The exception occurs when a user does not have the

permission to request operation on a resource.

SEVERITY HIGH

REPRODUCE THE ERROR Perform an operation on a resource when a user does not

have access rights.

RESOLUTION Grant access rights to the user on a resource.

POINT OF CONTACT NA

-19: FAILURE_MALFORMED_INPUT

MESSAGE Malformed input



-19: FAILURE_MALFORMED_INPUT

DESCRIPTION The exception occurs on findingmalformed input while

validating and decoding the install Info JWT.

SEVERITY HIGH


RESOLUTION NA


-20: FAILURE_EXTERNAL

MESSAGE Failure from external IdP

DESCRIPTION The exception occurs:

l While parsing response from Custom IdP Provider

l While refreshing access token with IdP provider

l During token exchange with IdP provider

SEVERITY HIGH

REPRODUCE THE ERROR Pass an invalid auth code / refresh token to IdP provider

RESOLUTION Use valid auth code / refresh token

POINT OF CONTACT NA



-23: FAILURE_NO_TOKEN_FOUND

MESSAGE No tokens were found

DESCRIPTION The exception occurs when no data is found for a given

provider in session object for given Session Id.

SEVERITY HIGH


RESOLUTION NA

POINT OF CONTACT NA

-25: FAILURE_EXCEPTION

MESSAGE Exception occurred

DESCRIPTION The exception occurs when something goes wrong while:

l Creating either a User Profile or a Claims Token

l Fetching user profile (or) provider details (or) tenant

properties

SEVERITY HIGH


RESOLUTION Verify tenant / provider / user details




-26: FAILURE_PROVIDER_EXIST_FOR_APP

MESSAGE Providers exist for app, please pass provider and user

credentials info

DESCRIPTION The exception occurs when something goes wrong while

dealing with claims token.

SEVERITY LOW

REPRODUCE THE ERROR Usewrong provider details or user credential info.

RESOLUTION Verify provider details and user credential info.

POINT OF CONTACT NA

-27: FAILURE_PROVIDER_NOT_EXIST_IN_APP_SERVICES

MESSAGE Given provider does not exist in app services.

DESCRIPTION The exception occurs while fetching services with invalid

provider details.

SEVERITY LOW

REPRODUCE THE ERROR Fetch services with invalid provider details.

RESOLUTION Check if provider is attached to App.

POINT OF CONTACT NA



-28: FAILURE_CONSTRAINTS_VALIDATION

MESSAGE Constraints validation Failed


creating an app or a service.

SEVERITY LOW

REPRODUCE THE ERROR Try to create:

l An app with invalid ID/Name/Desc

l A service with invalid service name

RESOLUTION Provide valid details for app/service

POINT OF CONTACT NA

-31: FAILURE_GATEWAY_ERR_TOKEN_DESER

MESSAGE Invalid Token: De-serialization error

DESCRIPTION The exception occurs when something goes wrong during

token validation

SEVERITY LOW

REPRODUCE THE ERROR Use an invalid token to invoke service

RESOLUTION Use a valid token to invoke service

POINT OF CONTACT NA



-32: FAILURE_GATEWAY_METADATA_ERR

MESSAGE Token Validation Error: Could not get metadata.


invoking a service that passes some token.

SEVERITY LOW

REPRODUCE THE ERROR Use invalid token while invoking services

RESOLUTION Use a valid token

POINT OF CONTACT NA

-35: FAILURE_GATEWAY_TOKEN_EXPIRED

MESSAGE Invalid Token: Token Expired


invoking an auth service by passing some token.

SEVERITY LOW

REPRODUCE THE ERROR Invoke a service with an expired token

RESOLUTION Use a valid token

POINT OF CONTACT NA



-36: FAILURE_GATEWAY_ISSUER_NOT_TRUSTED

MESSAGE Invalid Token: Issuer not trusted for tenant <tenant>, Token

Issuer: < Token Issuer >, Trusted Issuer is <Trusted issuer>

DESCRIPTION The exception occurs if the token issuer is not trusted

SEVERITY HIGH

REPRODUCE THE ERROR Try to get token from an untrusted issuer.

RESOLUTION Get token from a trusted issuer (i.e. the trusted auth tenant).

POINT OF CONTACT NA

-37: FAILURE_GATEWAY_GET_TRUSTED_AUTH_TOKEN

MESSAGE Exception in getting Get Trusted Auth Token

DESCRIPTION The exception occurs while checking permissions on

URL/Resource (http://***/serivices/<service_id>/<operation_

id>).

SEVERITY MEDIUM

REPRODUCE THE ERROR NA (Internal error)

RESOLUTION NA




-40: FAILURE_GATEWAY_INVALID_RES_PATH

MESSAGE InvalidResourcePath: null or empty resource path

DESCRIPTION The exception occurs if the gateway lib receives invalid

resource URL (frommiddleware/Sync) while checking

permission of resource.

SEVERITY MEDIUM


RESOLUTION NA


-41: FAILURE_GATEWAY_INVALID_RESOURCE

MESSAGE Invalid resource namespace/path.

DESCRIPTION The exception occurs if the gateway lib receives invalid name

space for a resource while checking resource permission.

SEVERITY MEDIUM


RESOLUTION NA




-42: FAILURE_GATEWAY_INVALID_AUTH_URL

MESSAGE Auth Service Endpoint not set properly. Input: %s

DESCRIPTION The exception occurs when gateway lib receives an invalid

Auth URL (frommiddleware/Sync).

SEVERITY MEDIUM


RESOLUTION NA


-43: FAILURE_GATEWAY_INVALID_TENANT

MESSAGE Tenant Name is null or empty.

DESCRIPTION The exception occurs when gateway lib receives tenant ID as

null or empty (frommiddleware/Sync).

SEVERITY MEDIUM


RESOLUTION NA.


-44: FAILURE_GATEWAY_INVALID_MAP

MESSAGE Params map is null.



-44: FAILURE_GATEWAY_INVALID_MAP

DESCRIPTION The exception occurs when gateway lib receives invalid

gateway parameters (frommiddleware /Sync)

SEVERITY MEDIUM


RESOLUTION NA


-45: FAILURE_GATEWAY_INVALID_ACCOUNT_ID

MESSAGE Account ID is null or empty

DESCRIPTION The exception occurs when gateway lib receives invalid

account ID in gateway parameters (frommiddleware/Sync)

SEVERITY MEDIUM


RESOLUTION NA


-47: FAILURE_GATEWAY_TIMEOUT

MESSAGE Back end service request timed out



-47: FAILURE_GATEWAY_TIMEOUT

DESCRIPTION Auth did not receive response from back end in defined time.

The exception occurs when Auth requests for:

l Getting roles of users in accounts

l Exchanging claims token with back-end

(Salesforce/Google/Microsoft AD etc.)

l Getting back-end token (Salesforce/Google/Microsoft

AD etc.)

l Importing users/groups from AD

SEVERITY HIGH

REPRODUCE THE ERROR When Auth invokes a request to backend, delay the response

from back end.

RESOLUTION Make sure back end server responds in defined time

POINT OF CONTACT NA

-48: FAILURE_BAD_REQUEST

MESSAGE Invalid input

DESCRIPTION The exception occurs if the request sent by the client (mf

console/accounts) to the Auth is malformed. Request could

be to create/update/delete

app/role/provider/environment/tenant properties etc.

SEVERITY HIGH



-48: FAILURE_BAD_REQUEST

REPRODUCE THE ERROR Send request to Auth to create/update/delete:

l Appwith invalid app ID

l Role with invalid role ID

l Provider with invalid provider ID/Name etc.

RESOLUTION Check request parameters


-49: FAILURE_GATEWAY_UNAUTHORIZED

MESSAGE User is unauthorized to perform the operation

DESCRIPTION The exception occurs when gateway lib receives request for

backend:

l Log-in with invalid credentials

l Metadata with invalid issuer uri/tenant context

SEVERITY HIGH

REPRODUCE THE ERROR Send request to gateway with invalid data to login or fetch

meta-data from backend.

RESOLUTION Verify credentials or issuer uri or tenant details etc.

POINT OF CONTACT NA



-50: FAILURE_PROVIDER_COMMUNICATION

MESSAGE Error communicating with provider


authenticating user against a Provider.

SEVERITY HIGH

REPRODUCE THE ERROR Configure provider with wrong settings

RESOLUTION Verify provider configurations

POINT OF CONTACT NA

-51: FAILURE_ADMISSION_DISALLOWED

MESSAGE User creation disallowed by Provider Admission Policy

DESCRIPTION For on-premise setup, user creation/updating failed post

successful accounts.auth login because AdmissionType is

Post_Login and ProviderAdmissionPolicy is pre_login_

approval_needed

SEVERITY MEDIUM


RESOLUTION NA




-52: FAILURE_GATEWAY_ERR_GET_SECURITY_ATTRIBUTES

MESSAGE Exception in fetching security attributes

DESCRIPTION The exception occurs when gateway lib receives request to

fetch security attributes with invalid Auth token.

SEVERITY MEDIUM

REPRODUCE THE ERROR Fetch security attributes with an invalid Auth token

RESOLUTION Pass a valid Auth token

POINT OF CONTACT NA

-53: FAILURE_GATEWAY_ERR_GET_USER_ATTRIBUTES

MESSAGE Exception in fetching user attributes.

DESCRIPTION The exception occurs when gateway lib receives request to

fetch user attributes with invalid Auth token.

SEVERITY MEDIUM

REPRODUCE THE ERROR Fetch user attributes with an invalid Auth token

RESOLUTION Pass a valid Auth token

POINT OF CONTACT NA

-55: FAILURE_SESSION_INVALID

MESSAGE Session Invalid.



-55: FAILURE_SESSION_INVALID

DESCRIPTION The exception occurs when session data is not retrieved for a

given session ID from backend. (backend could be accounts

as well).

SEVERITY MEDIUM

REPRODUCE THE ERROR Make a request to fetch session data with invalid session

(expired)

RESOLUTION Pass a valid session ID

POINT OF CONTACT NA

-56: FAILURE_BACKEND_TOKENS_TOO_LARGE

MESSAGE Back-end Token(s) are too large.

DESCRIPTION The exception occurs in backend response if the size of User

Data/User Attributes/Security Attributes is > 64 kb.

SEVERITY HIGH

REPRODUCE THE ERROR Request the back-end to fetch User Data/User

Attributes/Security Attributes with size >64 kb

RESOLUTION Make sure that backend does not fetch User Data/User

Attributes/Security Attributes with size >64 kb

POINT OF CONTACT NA



-57: FAILURE_GATEWAY_ERR_GET_PROFILE

MESSAGE Exception in fetching User Profile.

DESCRIPTION Failed to fetch user profile because the token has expired (or

invalid token issuer url).

SEVERITY MEDIUM

REPRODUCE THE ERROR Fetch user profile with invalid token/issuer URL

RESOLUTION Verify token/issuer URL

POINT OF CONTACT NA

-58: FAILURE_GATEWAY_ERR_LOGIN

MESSAGE Log-in failure.

DESCRIPTION Log-in request made to the gateway lib fails due to invalid

login parameters (APP_KEY/ APP_

SECRET/USERID/PASSWORD/PROVIDERID).

SEVERITY MEDIUM

REPRODUCE THE ERROR Make login request to gateway lib with invalid login

parameters.

RESOLUTION Verify login parameters.

POINT OF CONTACT NA



-59: FAILURE_GATEWAY_ERR_LOGOUT

MESSAGE Log-out failure.

DESCRIPTION Log-out request made to gateway lib fails due to invalid Auth

token.

SEVERITY MEDIUM

REPRODUCE THE ERROR Make log-out request to gateway lib with invalid token.

RESOLUTION Verify Auth token.

POINT OF CONTACT NA

-60: FAILURE_GATEWAY_INVALID_RES_PERM

MESSAGE Invalid resource permission.

DESCRIPTION The exception occurs when client makes a request

(tid.svctype/myresources/myresource1) to Gateway lib to

access a resource. Gateway lib validates if the resources are

permitted to give access. If the validation fails, then the error

occurs. Requested permission can beGET/PUT/POST etc.

or even custom permission such as Manage/Customize.

SEVERITY HIGH

REPRODUCE THE ERROR Access a resource which has no access permissions .

RESOLUTION Provide access permissions.

POINT OF CONTACT NA



-62: FAILURE_COMMUNICATION_ACTIVE_DIRECTORY

MESSAGE Could not connect to Active directory.

DESCRIPTION The exception occurs when AD is down, but the user tries to

authenticate against it.

SEVERITY HIGH

REPRODUCE THE ERROR Bring AD down and try to authenticate.

RESOLUTION Make sure AD is up and running.

POINT OF CONTACT NA

-63: FAILURE_INVALID_DOMAIN

MESSAGE Invalid Active Directory Domain.

DESCRIPTION The exception occurs if the configuration of AD domain name

is wrong.

SEVERITY HIGH

REPRODUCE THE ERROR Usewrong domain namewhile configuring AD

RESOLUTION Provide correct AD domain name

POINT OF CONTACT NA

-64: FAILURE_SSO_NOT_ENABLED_FOR_APP_PROVIDER

MESSAGE SSO is not enabled for app on associated provider.



-64: FAILURE_SSO_NOT_ENABLED_FOR_APP_PROVIDER

DESCRIPTION The exception occurs when a user tries to perform SSO login

when SSO is not enabled for the app.

SEVERITY HIGH

REPRODUCE THE ERROR Try to do SSO login when SSO is not enabled for the app.

RESOLUTION Enable SSO for the app.

POINT OF CONTACT NA

-65: FAILURE_INVALID_INPUT

MESSAGE Some of the input parameters provided are invalid.

DESCRIPTION The exception occurs when invalid input parameter is passed

while:

l Fetching Auth Provider details using provider name

l Changing password (if new password does not match

with regular strong password constraints)

l Fetching Account Users if account GUID passed as

null

SEVERITY MEDIUM

REPRODUCE THE ERROR Pass invalid input parameters while fetching Account users/

Auth Provider details/ changing password.

RESOLUTION Make sure valid input parameters are passed

POINT OF CONTACT NA



-67: FAILURE_NO_USER

MESSAGE No users found

DESCRIPTION User is inactive/unavailable in AD, but tried to authenticate

with the same user details.

SEVERITY HIGH

REPRODUCE THE ERROR Try to authenticate using inactive/deleted user in AD.

RESOLUTION Activate the user in AD.

POINT OF CONTACT NA

-68: FAILURE_TOKEN_ENDPOINT_OAUTH2

MESSAGE "Failed while invoking token endpoint." + "Recheck token

endpoint, Client Authentication scheme and client secret"

DESCRIPTION The exception occurs while fetching OAUTH2 token.

OAUTH2 endpoint is down (or) invalid client secret (or) client

authentication scheme constraints.

SEVERITY HIGH

REPRODUCE THE ERROR Fetch token by bringing downOAUTH2 endpoint or using

invalid client secret/ authentication scheme

RESOLUTION Verify client secret, authentication scheme, and endpoint

connectivity.

POINT OF CONTACT NA



-69: FAILURE_PROFILE_ENDPOINT_OAUTH2

MESSAGE "Failed while invoking profile endpoint. " + "Please check its

reachable and access is allowed in the OAuth app".

DESCRIPTION The exception occurs while fetching profile information.

Either the profile endpoint is down or an invalid OAuth token

was used.

SEVERITY HIGH

REPRODUCE THE ERROR Fetch profile info by bringing down the profile endpoint or

using invalid oauth token.

RESOLUTION Verify oauth token and profile endpoint.

POINT OF CONTACT NA

-70: FAILURE_MULTIPLE_USERS

MESSAGE Multiple users with same user name are found.

DESCRIPTION The exception occurs if multiple users are found for a given

user name in AD.

SEVERITY HIGH

REPRODUCE THE ERROR Createmultiple users with same user name in AD and try to

login with that user name.

RESOLUTION Make sure that only one user is available in AD for a given

user name.

POINT OF CONTACT NA



-71: FAILURE_INVALID_PROVIDER_OR_CREDENTIALS

MESSAGE Invalid Provider Configuration or User Credentials.

DESCRIPTION The exception occurs when a user tries to login against

Salesforce endpoint either due to invalid credentials or wrong

provider configuration.

SEVERITY HIGH

REPRODUCE THE ERROR Log-in to Salesforce endpoint with invalid credentials or

wrong provider configuration.

RESOLUTION Check provider configuration and user credentials

POINT OF CONTACT NA

-72: FAILURE_INVALID_CREDENTIALS_AD

MESSAGE Wrong Username/Password is provided for AD connection.

DESCRIPTION The exception occurs when a user logs in to AD with wrong

username/password.

SEVERITY HIGH

REPRODUCE THE ERROR Log-in to AD with wrong user credentials.

RESOLUTION Use valid user credentials.

POINT OF CONTACT NA



-73: FAILURE_INVALID_CREDENTIALS_OPENLDAP

MESSAGE Wrong Username/ Password is provided for OpenLDAP

connection

DESCRIPTION The exception occurs when a user logs in to OpenLDAP

endpoint using wrong username/password.

SEVERITY HIGH

REPRODUCE THE ERROR Log-in to Open LDAP endpoint using wrong user credentials

RESOLUTION Use valid user credentials

POINT OF CONTACT NA

-74: FAILURE_INVALID_CONFIGURATION_AD

MESSAGE Cannot connect to AD. Please ensure correct URL and

correct distinguished name are provided for the domain.

DESCRIPTION The exception occurs when a user logs in to AD using either

invalid URL or domain name.

SEVERITY MEDIUM

REPRODUCE THE ERROR Log-in to AD with invalid URL or domain name.

RESOLUTION Use valid URL and domain name

POINT OF CONTACT NA



-75: FAILURE_INVALID_CONFIGURATION_OPENLDAP

MESSAGE Cannot connect to OpenLDAP. Please ensure correct URL,

DN, and Federation ID are provided for the domain.

DESCRIPTION The exception occurs when a user logs in to OpenLDAP

using either invalid URL, domain name, or federation ID.

SEVERITY MEDIUM

REPRODUCE THE ERROR Log-in to AD using invalid URL, domain name, or federation

ID

RESOLUTION Use correct URL, domain name, and federation ID.

POINT OF CONTACT NA

-76: FAILURE_INTERNAL_EXCEPTION_AD

MESSAGE Internal exception occurred while authenticating to AD.

DESCRIPTION The exception occurs when something goes wrong internally

while authenticating with AD. The error does not fall under

FAILURE_INVALID_CREDENTIALS_AD and FAILURE_

INVALID_CONFIGURATION_AD.

SEVERITY HIGH


RESOLUTION NA




-77: FAILURE_INTERNAL_EXCEPTION_OPENLDAP

MESSAGE Internal exception occurred while authenticating to

OpenLDAP.

DESCRIPTION The exception occurs when something goes wrong internally

while authenticating with OpenLDAP. The error does not fall

under FAILURE_INVALID_CREDENTIALS_OPENLDAP

and FAILURE_INVALID_CONFIGURATION_OPENLDAP.

SEVERITY HIGH


RESOLUTION NA

POINT OF CONTACT NA

-80: FAILURE_INVALID_DN

MESSAGE Unable to parse DN or Invalid Domain


making test connection against LDAP endpoint due to invalid

domain name.

SEVERITY HIGH

REPRODUCE THE ERROR Provide invalid domain namewhile authenticating against

LDAP endpoint.

RESOLUTION Verify domain name.

POINT OF CONTACT NA



-81: FAILURE_TEST_CONNECTION_NOT_SUPPORTED

MESSAGE Test Connection is not supported for this provider.

DESCRIPTION In Kony Fabric console, while defining identity service, user

can test connection. The error occurs if the backend does not

allowed the user to test connection.

SEVERITY LOW


RESOLUTION NA

POINT OF CONTACT NA

-82: FAILURE_DIAGNOSTICS

MESSAGE Error in collecting diagnostic information.


collecting the diagnostic data like timestamp, OS, CPU, free

memory, processor count, Java details, time zone, andMF

version etc.

SEVERITY MEDIUM


RESOLUTION NA

POINT OF CONTACT NA



-83: FAILURE_AUTHORIZATION_CODE_MISSING

MESSAGE Authorization code is missing in request body.

DESCRIPTION The exception occurs in OAuth2.0 flow, if authorization code

is missing in a request sent by client to the Authorization

server to get access token.

SEVERITY HIGH

REPRODUCE THE ERROR Get access token without passing authorization code.

RESOLUTION Pass authorization code.

POINT OF CONTACT NA

-84: FAILURE_REFRESH

MESSAGE Failed to refresh the token. Check if refresh is supported by

backend.


refreshing/fetching the access token using the refresh token.

The refresh token is invalid or backend does not support

refresh.

SEVERITY HIGH

REPRODUCE THE ERROR Try to refresh/fetch the access token using invalid refresh

token.

RESOLUTION Use valid refresh token.

POINT OF CONTACT NA



-86: FAILURE_LICENSE_NOT_ACTIVATED

MESSAGE License is not activated.

DESCRIPTION The exception occurs when account invokes license APIs

but the license is not activated.

SEVERITY CRITICAL


RESOLUTION NA


-87: FAILURE_LICENSE_ALREADY_ACTIVATED

MESSAGE License is already activated. Cannot activatemore than

once.

DESCRIPTION The exception occurs when a user tries to activate the

license that is already activated.

SEVERITY LOW

REPRODUCE THE ERROR Try to activate the license which is already activated.

RESOLUTION Do not try to activate the license which is already activated.

POINT OF CONTACT NA



-88: FAILURE_LICENSE_PUBLIC_KEY_ABSENT_IN_REQUEST

MESSAGE No public key found in the request.

DESCRIPTION The exception occurs when an account invokes license API

without providing the public key.

SEVERITY HIGH


RESOLUTION NA


-89: FAILURE_LICENSE_INFO_ABSENT_IN_REQUEST

MESSAGE No license info found in request.


without providing the license information.

SEVERITY HIGH


RESOLUTION NA


-90: FAILURE_LICENSE_TAMPERED_KEY

MESSAGE Public key is found to be tampered.



-90: FAILURE_LICENSE_TAMPERED_KEY


with a tampered public key.

SEVERITY CRITICAL


RESOLUTION NA


-91: FAILURE_LICENSE_TAMPERED_DATA

MESSAGE License data is found to be tampered


with tampered license information.

SEVERITY CRITICAL


RESOLUTION NA


-92: FAILURE_LICENSE_NOT_FOUND

MESSAGE License info is not found



-92: FAILURE_LICENSE_NOT_FOUND

DESCRIPTION The exception occurs if publishMeta is not present (happens

when upgraded from 7.2) in license app or the license app

does not exist (happens when upgraded from 7.1 or earlier).

SEVERITY HIGH


RESOLUTION NA


-93: FAILURE_NO_SSO_PROFILE

MESSAGE Linking identities failed due to null session puid. Check if the

SSO provider%s has enabled user profile.

DESCRIPTION The exception occurs in linked identity SSO flow when one of

the providers has profile endpoint type as none.

SEVERITY HIGH

REPRODUCE THE ERROR In linked identity SSO flow, disable profile access in one of

the providers.

RESOLUTION Check if profile access is enabled in all providers.

POINT OF CONTACT NA



-94: FAILURE_INVALID_EXTERNAL_PROVIDER

MESSAGE "Provider config invalid. Check that provider%s is of type

OAuth2, has profile" + "enabled and email attribute is

configured."

DESCRIPTION The exception occurs while accessing user profile data.

Either the provider is not allowed for external authentication

(or) no profile is configured (or) no email attribute selector is

configured.

SEVERITY HIGH

REPRODUCE THE ERROR Try to access user profile data when the provider is not

allowed for external authentication (or) no profile is configured

(or) no email attribute selector is configured.

RESOLUTION Make sure the provider is allowed for external authentication,

profile is configured, and email attribute selector is

configured.

POINT OF CONTACT NA

-95: FAILURE_LICENSE_INFO_TAMPERED_IN_REQUEST

MESSAGE License Info tampered in request.

DESCRIPTION The exception occurs when the license data is tampered in

the request made to access license API in order to

activate/update/get license info

SEVERITY CRITICAL




-95: FAILURE_LICENSE_INFO_TAMPERED_IN_REQUEST

RESOLUTION NA


-96: FAILURE_MISSING_EXTENSION_GRANT_TYPE

MESSAGE Missing extension grant type value.

DESCRIPTION The exception occurs after setting the extension grant type to

OAuth2ProviderConfig object when extension grant type is

configured as none.

SEVERITY HIGH

REPRODUCE THE ERROR Authenticate against OAuth2.0 by providing extension grant

type as none.

RESOLUTION Verify and provide valid extension grant type.

POINT OF CONTACT NA

-97: FAILURE_INSUFFICIENT_PRIVILEGE

MESSAGE User has insufficient privilege for this operation.

DESCRIPTION The exception occurs when setup API is invoked by a user

who does not have appropriate role for performing the action.

SEVERITY MEDIUM

REPRODUCE THE ERROR Set the user role as not allowed to invoke setup API.



-97: FAILURE_INSUFFICIENT_PRIVILEGE

RESOLUTION Give permission to the user to invoke setup API.

POINT OF CONTACT NA

-98: FAILURE_ACCOUNT_USERS

MESSAGE Failure occurred while fetching users of account.

DESCRIPTION The exception occurs on failing to fetch users of an account

with the given guid.

SEVERITY HIGH


RESOLUTION NA


-99: FAILURE_INVALID_JWT_SIGNATURE

MESSAGE JWT Signature validation failed.


verifying token string signature and decoding it. Account

passes the token to activate and update the license on cloud.

SEVERITY HIGH




-99: FAILURE_INVALID_JWT_SIGNATURE

RESOLUTION NA


-100: FAILURE_GATEWAY_FETCH_LICENSE_MAP

MESSAGE Failure occurred while fetching licensemap.


fetching the license data from gateway lib. The HTTP status

will not be 200 or 401.

SEVERITY HIGH


RESOLUTION NA


-101: FAILURE_LICENSE_RECIPIENT_CERT_ABSENT_IN_REQUEST

MESSAGE No recipient cert found in request

DESCRIPTION Recipient cert is not found in the request made to fetch

license.

SEVERITY HIGH

REPRODUCE THE ERROR Send request (missing recipient cert) to fetch license .



-101: FAILURE_LICENSE_RECIPIENT_CERT_ABSENT_IN_REQUEST

RESOLUTION Make sure recipient cert is available in request.

POINT OF CONTACT NA


Kony Error Codes · ComponentsErrorCodes Version1.0 RevisionHistory Date DocumentVersion...

Documents

Transcript of Kony Error Codes · ComponentsErrorCodes Version1.0 RevisionHistory Date DocumentVersion...