# Remote Roster Plugin Readme

## Overview

This plugin will implement the proto-XEP, Remote Roster, discussed here. Basically it's purpose is to allow an external component full control over the part of a roster it's assigned. For example, if the AIM transport is at aim.example.org, you can allow that transport to make whatever modifications it needs without involving the end user. This is especially useful so that a user does not get flooded with subscription requests upon registration. This plugin also implements a few minor extensions that Kraken used to implement for Spark, though those are optional.

## Installation

Copy remoteRoster.jar into the plugins directory of your Openfire installation. The plugin will then be automatically deployed. To upgrade to a new version, copy the new remoteRoster.jar file over the existing file.

## Configuration

The Remote Roster plugin can be configured under "Server"-"Server Settings"-"Remote Roster".