Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

About this error message

Users will encounter this error message when attempting to use a feature of Profound.js that connects to an IBM i or external database, but have not first logged into a valid IBM i session. To correct this issue, make sure a valid IBM i connection is created prior to using the Profound.js feature that connects to the IBM i or external database.


How to create a valid connection.

Log in when running an initial module.

When an initial module is started by a user visiting a URL alias, under the default settings, the user will be prompted to enter their IBM i credentials to log into the server. Upon the user entering valid credentials, connection will be created to the IBM i system for this user's session.

Create connector credentials.

For applications that will not prompt the user to log in, like for web-services, a set of default credentials can be specified in the Profound.js server's configuration file, and a valid session will attempt to be created from these stored credentials. To specify these credentials you must first use the the store_credentials command line utility to create the encrypted credential file. Then you can use the connectorCredentials configuration setting to specify the location of the encrypted credential file.

Pass 'auth' token from another valid session.

When calling Profound.js applications from another application that is already connected to a valid session, you can use the authentication token from the calling application to create a valid connection for your new application. When calling the Profound.js application from Genie or a Rich Display File application, this 'auth' token is automatically added included in the call to the Profound.js application.

  • No labels