Netvibes CloudView Configuration

Connector Configuration

To push items into Netvibes CloudView, you first have to register the connector within your Netvibes CloudView instance.

First, navigate to the Netvibes CloudView Admin Console of your instance under http://<CLOUDVIEW_INSTANCE_HOST>:10001/admin/#home where CLOUDVIEW_INSTANCE_HOST is the Host of your Netvibes CloudView instance.

Once you’re in the Admin Console, navigate into Connectors under Index on the left sidebar. Here you can add a new connector via Add connector.
cloudview setup connector add
When configuring the connector, set the connector Type to Unmanaged (Push API).
cloudview setup connector config
Don’t forget to save and apply the new connector.
cloudview setup connector save apply

From this point on you could already push items into Netvibes CloudView. Most likely, you will want to set up a Security Source before you proceed though.

Security Source Configuration

A security source is necessary to provide Netvibes CloudView with security information and distinguish between who can and can’t see an item within Netvibes CloudView. Netvibes CloudView offers different options for Security Sources, as for example a Microsoft Active Directory Security Source. For more information on that, please refer to your Netvibes CloudView documentation.

Alternatively, the connector generates security tokens in the form of remote:<ID> which can be used in conjunction with a Remote HTTP Security Source.

To start, navigate to Security Sources under Search on the left sidebar.

cloudview setup security add

Remote HTTP Security Source

Make sure to choose the Type Remote Http.
cloudview setup security config
Configure the isAlive and service path as /security/ and set the retries as required. As host set your Raytion Custom Security Manager (CSM) instance.
cloudview setup security adv config
Make sure do save and apply after you’re done.
cloudview setup security save apply
The connection to a Remote HTTP security source is an unsecured HTTP request. Therefore, it is not recommended to employ any remote security sources for password validation. Instead, use remote security sources in combination with an Active Directory Security Source that does the authentication. In this case, remote security source will only be asked to provide ACLs for a given username. For this, Active Directory must be the first security source configured in the Mashup-UI. Further, authenticate to FIRST must be chosen