verify-session-backend

verify-session-backend is a copious-transitions-apps package. This package handles session verification for calling processes. Most of the processes are expected to be back-end processes rather than web cients. Sessions are based upon Intergalactic Identities.

The npm page: verify-session-backend

verify-session-backend checks on a session and responds positively if the session is current, otherwise negatively.

copious-transitions is a generalized framework for handling state transtitions from web clients as well as from message-relay-services endpoints. copious-transitions-apps are descendants of the CopiousTransitions class exported from copious-transitions

Intergalactic identities may be obtained on the of-this.world website. At the following address: of-this.worldig/igid-creator/

Installation

verify-session-backend is an npm package: verify-session-backend

The verify-session-backend package provides a bash command line which can be accessed if the package is installed globally as such:

npm install -g verify-session-backend

This installation will create a script link in the bin directory configured for your npm. You should be able to confirm its installation with the following command:

which igid-session-verifier

running the program

The igid-session-verifier program will run if a configuration file can be read from the working directory. If the working directory contains a configuration file with the name, verify-B-session-service.conf the program can be run by just entering the command name:

igid-session-verifier

Otherwise, a configuration file must be specified:

igid-session-verifier custom.conf

Making connections

igid-session-verifier may start up with default connections to databases and services. But, the connections may be set after it starts listening on all of its servers.

The way to make custom connections to services (likely better than the defaults) is to make use of the tool, com_link_manager. The tool can be installed on your system using npm as such:

npm install -g com_link_manager

Then, run this command with a configuration file name parameter (required).

com_link_manager link_construction_conf.conf

The configuration files for this tool are JSON formatted instructions telling the target program (running program) what classes to load, instantiate, and initialize.

Refer to com_link_manager for examples.

Siblings

verify-session-backend will check to see if a session is active. The session will be one that has been created by captcha-igid.

verify-session-backend provides session verification operations for websites and backend processes that are authorized by captcha-igid. verify-session-backend will not operate outside of the captcha-igid context.

copious-transitions-apps provides a few other programs that can share session information managed by verify-session-backend.

Here is a list of some other npm packages for running associated processes for uploading and asset access:

• captcha-igid
• publication-igid
• media-up-igid
• media-up-lite-igid
• counter-access-igid

Web Service

verify-B-session filters traffic for configured backend services based upon the presence of a session for an Intergalactic ID (igid);

Any requests on media and transitions pathways will be checked for a session against the shared session table initiated by the captch-igid process.

The aim here is to have transitions be mostly configured (not built in). The activity of a transition engine supplied by this package is minimal, only serving to verify the operation actions of the endpoint processes an instance of this process discovers in its configuation.

Some architectural points

1. Transitions generally pass things on to endpoints and handle responses.

2. There is little or no database connectivity from this process other than the shared session table.

3. This process can supply static media retrieval, but that might be better left to another copious-transition-app.

4. This process will do little to supply dynamic media. Its dynamic media might set up shared transition tokens. However, the transitions mostly have to do with endpoint processing, so this will not be too common.

5. This is not a user login/registration process. A session must be established already for requests to pass through.