InSight user and agency management


Template level External Article ID

KBA00023107

Issue

Logging into the Insight broker and adding a user to Insight

Resolution

Logging into the InSight Broker

To log into your InSight broker:

  1. Open a web browser, and then enter one of the following:
    • localhost:8080/InSight, where localhost is the name of your server or the IP address
    • InSightserverIP:8080/InSight, where InSightserverIP is the IP address of the InSight server
  2. A login page opens, where you'll use your InSight credentials to log in. Normally, these match your Spillman credentials, but they are stored separately.

NOTE: Internet Explorer 9 or a newer IE in compatibility mode is recommended. Add the InSight broker website to the list of websites for Compatibility View. The screen shot provides an idea of how to do this, but you should use IE's help documents for complete instructions.

in1.png

NOTE: Help with reaching a 3rd-party Admin page for InSight using localhost and port forwarding:
At times reaching the webpage for Insight (e.g., http://localhost:8080/InSight) may not work, especially if the SAA/Admin doesn't have credentials established to access the broker directly (e.g., http://{brokerhostIP}:8080/InSight). 
A simple solution is to create a port forwarding for localhost through PuTTY (e.g. localhost:8080 forwards to port 8080). This will allow the user to launch an ssh connection through PuTTY from their desktop to their Spillman Server and then connect to their 3rd party site through a web browser at http://localhost:8080/InSight/... for administration of accounts.


Adding a User to InSight

  1. Click the USERS button at the top of the page to see the list of users for your agency. If this is the first time you are adding users, the list will be blank
  2. Click Add User

    in2.png

     
  3. Enter the user's credentials (preferably matching their Spillman credentials) and select their role.

    in3.png

    By default, the Role field is set to Agency Admin because it's the top entry in the list. Make sure to verify that this value is set properly before clicking Add User.
    Agency Admins administer over agencies, and can modify their agency's users and their own agency details.
    Broker Admins are only able to be created by broker admins themselves, and have the capability to administer over the entirety of the broker (This role is usually reserved for Spillman employees).
    Users are capable of querying the database, but not modifying records in the admin utility. This role is the standard role most users need.

     
  4. Click Add User

Adding an Agency to InSight

  1. Click the AGENCIES button at the top of the page to see the list of agencies for your broker.

    in4.png

     
  2. Click Add Agency

    in5.png

     
  3. Add the requested information as necessary.

    Type: Connection type between agency/broker. Typically, direct is used, which uses a socket connection, set up on the agency's DataExchange.
    ID: Unique identifier for InSight's use. Usually the agency's mnemonic.
    Name: The agency's name.
    Active: Marks agency as active/non-active. Non-active agencies cannot use InSight.
    IP Address/Port: This is the IP address and port that the broker will use to receive/return XML sent to it. This is the agency's IP.
    Admin Email: This email address will be sent messages if something goes wrong in the communication between agency and broker.
    Agency Contacts: Not required, but certainly convenient.

     
  4. Once you save the agency, these dialog boxes and lists open on the bottom of the page:

    in6.png

     
  5. The first allows you to assign unassigned users to this agency, as well as lists the current users.
  6. The second is required for clients to query the InSight database. This allows either IP addresses (SINGLE) or ranges (NETWORK) to query the InSight broker. If a client tries to query the broker without being on this list, it will not work.
  7. When defining a NETWORK, put an asterisk in place of the last octets so it allows everything over the defined subnet. For example, this image shows a configuration that would allow every IP address querying the broker whose first three octets are 10.20.10:

    in7.png