RapidIdentity Product Guide: Legacy UI

Managing Community Adapters

  1. If a community adapter JAR file was installed in Common Libraries, it can be accessed in any of the following three methods in RapidIdentity Connect.

    1. Log out of RapidIdentity Connect and then log in to RapidIdentity Connect.

    2. Refresh the RapidIdentity Connect browser tab.

    3. Click Other > Refresh all.

Choice c allows the current Actions module Action Set editor tabs to remain open and is likely the most efficient approach.

Caution

If a community adapter is deployed into the same instance or cluster where it was created, the actions in the new adapter will take precedence and the original Action Sets will no longer be visible. Therefore, additional editing and exporting of the Action Sets that make up the adapter won't work without first removing the adapter from RapidIdentity Appliance > Server Management > Data > Common Libraries and restarting Tomcat.

If a community adapter is deployed into the same instance or cluster where it was created, the actions in the new adapter will take precedence and the original Action Sets will no longer be visible. Therefore, additional editing and exporting of the Action Sets that make up the adapter won't work without first removing the adapter from RapidIdentity Appliance > Server Management > Data > Common Libraries and restarting Tomcat.

After the community adapter is installed, the community adapter actions can be located by dynamically searching for the community adapter by name in RapidIdentity Connect or navigating to the Community Adapter folder. In the screen shots below, the HipChat community adapter is a representative example.  

Legacy_Hipchat_Community_Adapter_1.png
Legacy_Hipchat_Community_Adapter_2.png