vocera ldap adapter configuration guide

Vocera LDAP Adapter Configuration GuideVersion 2.0.0

ii VOCERA LDAP ADAPTER CONFIGURATION GUIDE

Notice

Copyright © 2002-2021 Vocera Communications, Inc. All rights reserved.

Vocera® is a registered trademark of Vocera Communications, Inc.

This software is licensed, not sold, by Vocera Communications, Inc. (“Vocera”). The reference text of the license governing this software can be found at https://www.vocera.com/legal/. The version legallybinding on you (which includes limitations of warranty, limitations of remedy and liability, and other provisions) is as agreed between Vocera and the reseller from whom your system was acquired and is availablefrom that reseller.

Certain portions of Vocera’s product are derived from software licensed by the third parties as described at https://www.vocera.com/legal/.

Microsoft®, Windows®, Windows Server®, Internet Explorer®, Excel®, and Active Directory® are registered trademarks of Microsoft Corporation in the United States and other countries.

Java® is a registered trademark of Oracle Corporation and/or its affiliates.

All other trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owner/s. All other brands and/or product names are the trademarks (or registeredtrademarks) and property of their respective owner/s.

Vocera Communications, Inc.www.vocera.comtel :: +1 408 882 5100fax :: +1 408 882 5101

Last modified: 2021-05-01 09:25

ADP-ldap-200-Docs build 314

https://www.vocera.com/legal/

https://www.vocera.com/legal/

iii VOCERA LDAP ADAPTER CONFIGURATION GUIDE

Contents

Understanding a Vocera LDAP Adapter Configuration.............................................................................................................4

Viewing the Vocera LDAP Adapter Requirements........................................................................................................................................ 5

Configuring a Vocera LDAP Adapter.............................................................................................................................................. 8

Synchronizing Users and Groups.................................................................................................................................................. 14

Understanding Adapter Installation............................................................................................................................................... 16

Accessing Supported Adapters.................................................................................................................................................................. 16

Recreating a Repository............................................................................................................................................................................. 17

Installing an Adapter................................................................................................................................................................................... 18

Practicing an Adapter Installation............................................................................................................................................................... 18

Navigating the Vocera Platform Adapters...................................................................................................................................20

Editing an Adapter......................................................................................................................................................................................22

Creating a New Adapter.............................................................................................................................................................................22

Saving an Adapter......................................................................................................................................................................................24

Deactivating an Adapter............................................................................................................................................................................. 24

Removing an Adapter.................................................................................................................................................................................25

4 VOCERA LDAP ADAPTER CONFIGURATION GUIDE

Understanding a Vocera LDAP Adapter Configuration

Configure a Vocera LDAP Adapter to enable the customer to use single sign on authentication in the system.

Adapters send information to and receive information from the Vocera Platform, as well as monitor and collect data. Each adapter isconfigured to allow Vocera Platform to communicate with a specific type of resource and any devices that resource may control. Forexample, the Vocera LDAP Adapter connects to an LDAP server to provide authentication, and to retrieve and map LDAP users to VoceraPlatform users.

Vocera Platform provides the ability to connect to a Lightweight Directory Access Protocol (LDAP) server, allowing users to authenticatewith the same set of credentials they use elsewhere in their organization. The Vocera LDAP Adapter configuration settings allow facilityadministrators to use the organization's existing security configurations, rather than create unique users, groups, or security policies toaccess the Vocera Platform. Vocera Platform allows connection to only one LDAP server per organization.

A new LDAP user account is not visible in Vocera Platform until the new user logs into the system. If an organization uses PIN authorizationsecurity for devices, such as a Smartphone, the user will be prompted to create the PIN when they first log into the Vocera Platformplatform. Vocera Platform will not retrieve a user's PIN from the organization's LDAP server.

Vocera Platform leverages the organization's existing LDAP user and group configurations to manage access securely. The organization'sgroups can be assigned to membership in Vocera Platform groups. Retrieved LDAP groups are assigned membership in Vocera Platformroles and groups to manage system access.

The Vocera Platform appliance must be connected to the organization's LDAP server to retrieve available attributes and groups. Oncecollected, you can edit the mappings that pair the data stored in the organization's LDAP server with system attributes in order to allowusers to authenticate in Vocera Platform. Vocera Platform supports most LDAP servers, including Microsoft Active Directory (AD).

LDAP servers and clients communicate by defining a directory service and access to the service. A directory service information tree (DIT)is composed of entries that have a set of named components called attributes to hold the data for that entry. An attribute consists of itsname, a type, and the value for the attribute. A schema specifies the attributes for the entries in an LDAP server by defining the rules forwhich attributes may be used in an entry, the kinds of values that those attributes may have, and how clients may interact with thosevalues. These directory entries are arranged in a hierarchical structure, starting at a base entry, and then branching down into individualentries.

Each entry in a directory tree can be located by its distinguished name (DN). The DN consists of a string of relative distinguished names(RDNs). An RDN is composed of one or more attribute name and value pairs. For example, the RDN for the entry cn=John Smith containsthe attribute name of cn (common name) and the value of John Smith. A DN is composed of an entry’s RDN followed by all of the RDNs(separated by commas or semicolons) found while moving up the tree toward the base entry.

Warning: Creating a group on the LDAP server and mapping that LDAP group to USERS\DOMAIN USERS in Vocera Platform willprevent successful Vocera LDAP Adapter integration with the hospital LDAP server.

UNDERSTANDING A VOCERA LDAP ADAPTER CONFIGURATION


Users in LDAP need to be assigned to groups inside of Active Directory, other than the Domain Users group, for LDAP to work properlywith Vocera Platform. Domain Users is the primary group for users in Active Directory and this group's memberships are not visible viaLDAP as a "memberOf" user attribute. LDAP users have to be a member of a group created on the LDAP server for Vocera Platform to usein mappings, not the default Domain Users.

Viewing the Vocera LDAP Adapter RequirementsA Vocera LDAP Adapter uses these minimum requirements in a Vocera Platform installation.

SystemThe Vocera LDAP Adapter is designed to connect Vocera Platform to one LDAP server per organization.

PortPort 389/tcp is the port the Vocera Platform will use to communicate with the facility's LDAP server. Port 663/tcp is used for SSLcommunication.

DatasetsAn adapter defines a default Dataset structure in order to function. Attributes are organized by Datasets and store the information requiredby the adapter. Adapters use this data during the process of receiving and sending messages.

Not all adapters require Datasets to function. When an adapter does require Datasets, the system will determine if they already exist. If theydo not exist, the system will create the needed Datasets.

When creating or editing an adapter, use the following information to select the appropriate datasets in the Required Datasets section.

• The ACTORS Dataset stores all actors.

• The GROUPS Dataset stores all user groups.

• The GROUP_MEMBERS Dataset stores all the members in a group.

• The SITES Dataset stores all site information.

• The USERS Dataset stores all Vocera users.

ACTORS Dataset

Element Name Reverse Name Key Reverse Key Required Type Description

Link groups actor False True N/A One-to-many The ACTORSDataset islinked to theGROUP_MEMBERSDataset, andthe link order is1:n (one actorassociatedto manygroup_members)

GROUPS Dataset


Attribute name N/A True N/A N/A String Attribute thatstores the nameof the group.

Attribute ldap_dn N/A False N/A False String Attribute thatstores thedistinguishedname of thegroup in LDAP.




Link site groups True False N/A Many-to-one The GROUPSDataset is linkedto the SITESDataset, and thelink order is n:1(many groupsassociated to onesite)

Link members group False True N/A One-to-many The GROUPSDataset islinked to theGROUP_MEMBERSDataset, andthe link order is1:n (one groupassociatedto manygroup_members)

GROUP_MEMBERS Dataset


Link actor groups True False N/A Many-to-one TheGROUP_MEMBERSDataset is linkedto the ACTORSDataset, andthe link orderis n:1 (manygroup_membersassociated to oneactor)

Link group members True False N/A Many-to-one TheGROUP_MEMBERSDataset is linkedto the GROUPSDataset, andthe link orderis n:1 (manygroup_membersassociated to onegroup)

SITES Dataset


Attribute name N/A True N/A N/A String Attribute thatstores the uniquename for the site.

Link groups site False True N/A One-to-many The SITESDataset is linkedto the GROUPSDataset, andthe link orderis 1:n (one siteassociated tomany groups)

USERS Dataset


Attribute login N/A True N/A N/A String Attribute thatstores the loginname of the user.




Attribute active N/A False N/A False String Attribute thatstores whetheror not the user'saccount isenabled.

Attribute ldap_dn N/A False N/A False String Attribute thatstores internaluse only.


Configuring a Vocera LDAP Adapter

The Vocera LDAP Adapter settings enable direct communication between the adapter and the Vocera Platform.

Select an empty field and begin typing, or select an existing value and type over it. To keep an existing value, do not edit that field.

1. Access the Vocera Platform Web Console and navigate to the adapters.

See Navigating the Vocera Platform Adapters on page 20 for instructions.

2. Select New Adapter in the Action menu, or select an adapter you wish to configure and then select Edit, to display the configurationfields. The configuration fields are the same for new and existing adapters.

3. Navigate to the New Adapter option, or navigate to an existing adapter to edit. See Creating a New Adapter on page 22 andEditing an Adapter on page 22 for instruction as needed.

The configuration fields are the same for new and existing adapters.

CONFIGURING A VOCERA LDAP ADAPTER




4. Complete the configuration fields as described in the table.

Configuration Fields Description

Component Name Click the Component Name field to display a list of the systems anddevices that the Vocera Platform currently supports. Select the name ofthe adapter to create.

Reference Name Enter a short descriptive name in the Reference Name field to uniquelyidentify an adapter instance. It may demonstrate the adapter function orother information; for example, Production adapter may differentiate a liveadapter from a development or "sandbox" adapter.

Enabled Select the Enabled checkbox to allow the Vocera Platform to use the newadapter. The Vocera Platform ignores the adapter if this option is disabled.

Required Datasets If more than one dataset exists that meets the adapter's requirements,select the appropriate datasets for the new adapter to functioncorrectly. The system searches for the datasets that meet the adaptersrequirements. If the datasets already exist, the system will use them.If the datasets do not exist, the system will create them automatically.Select Create in the drop-down menu to create a new dataset to meet theorganization's requirements.

5. Complete the LDAP Settings configuration fields as described in the table.

Set up a connection to an LDAP or ActiveDirectory server to allow users to authenticate using the same credentials they do elsewherein the organization. Each configuration allows one LDAP server per organization. The LDAP Settings section displays example settingsfor server connections, and must be changed to the appropriate settings for the organization's LDAP server.

Note: Once you have entered the LDAP Settings information in this section, click the Save button at the bottom of the page. Inorder to retrieve the attributes and groups from the LDAP server, the adapter must first be active and running in the system.

LDAP Settings Configuration Field Description

Use Automatic Discovery Check the Use Automatic Discovery box to automatically discover theLDAP server(s) for the given base Distinguished Name (DN). Select thisoption instead of using the LDAP Server and Port settings describedbelow.

LDAP Server Enter the host name or IP address of the LDAP server hosting the facility'sdirectory service. Vocera Platform supports one LDAP server connectionper organization.

LDAP Port Enter the port, usually 389/tcp, that Vocera Platform will use tocommunicate with the facility's LDAP server. The LDAP port setting mustmatch the port set in the LDAP server.

Use SSL Check the SSL box to set the port to 636/tcp. Toggle this checkbox onand off to view the default port settings for the LDAP Port and Use SSLfields. Select the Use SSL checkbox to enforce Secure Sockets Layer(SSL) security for communication over the Internet when retrieving datafrom the directory service.



LDAP Settings Configuration Field Description

Base DN Enter the Distinguished Name (DN) for the top level entry in the LDAPdirectory. The base DN describes where to load users and groups.Some example entry names include CN=Users for the common nameattribute, or DC=example.com for a domain component attribute.This must be a domain partition root; other partitions, such as OU orOrganization Unit, will not synchronize properly.

DN of Schema Enter the Distinguished Name (DN) of the facility's LDAP schema to obtainthe set of rules governing what can be stored as entries in the LDAPdirectory. This allows Vocera Platform to retrieve attributes from LDAP tomatch to the Users dataset.

DN of Service Account Enter the DN of the LDAP Service Account for Vocera Platform to useto authenticate with the organization's server. Leave this field blank foranonymous access.

Service Account Password Enter the password for the LDAP Service Account for Vocera Platform touse to authenticate with the organization's server. Leave this field blank foranonymous access.

Site Select a Vocera Platform site name from the dropdown list. This site will belinked to all new users and groups.

Note: During synchronization, existing users will not be linked tothe selected site if they are already linked to a different site. SeeSynchronizing Users and Groups on page 14.

6. Complete the Read Attributes configuration fields as described in the table.

Read Attributes Configuration Fields Description

Retrieve Attributes and Groups Once connected to the LDAP server, you can read the attributes andgroups in the organization's directory service.Click Save at the bottom of the adapter page, if LDAP settings were justadded or changed. The Vocera LDAP Adapter must be running, and theconfiguration must be saved if new settings were applied, in order toaccess the service.Select the Retrieve Attributes and Groups button in the Read Attributesand Groups section to collect all configured attributes and groups fromthe LDAP server. The retrieval will take several minutes, depending on thequantity of data to transfer.

7. Complete the Attribute Mappings configuration fields as described in the table.



If a mapping has already been set up, the existing mapping will be validated against the new LDAP Attributes and new USERS DatasetAttributes. If the mapping is still valid (both the USERS Attributes and the LDAP Attributes exist), the user will be able to save the form. Ifany mapping is invalid (either a USERS Attribute or an LDAP Attribute doesn't exist) the user will not able to save the form.

The following default attributes are paired when there are no pre-existing mappings for the systems:

Engage maps to LDAP

USERS.login maps to LDAP.sAMAccountName

USERS.ldap_dn maps to LDAP.distinguishedName

USERS.first_name maps to LDAP.givenName

USERS.last_name maps to LDAP.sn

USERS.middle_initials maps to LDAP.initials

USERS.email maps to LDAP.mail

After the data is retrieved from the LDAP server, map Vocera Platform attributes to the retrieved LDAP attributes. The attributes loginand ldap_dn are required.

Attribute Mappings Configuration Fields Description

Vocera Attribute Select a mapping for a Vocera Platform attribute.

LDAP Attribute Select a mapping for an LDAP attribute.

8. Complete the Group Mappings configuration fields as described in the table.

At most one mapping should exist in each section for any particular LDAP group, although this is not enforced.

Group Mappings Configuration Fields Description

Vocera Group Name Select a mapping for a Vocera Platform Group. Enter the Vocera Platformgroup name to which an LDAP group will be mapped.Group names provide auto completion from the retrieved Vocera Platformgroups based on the configured site, but they can be any value (if aVocera Platform group does not exist for the group name, a new group willbe created and a warning will be shown).

LDAP Group Select a mapping for an LDAP Group. Choose from the LDAP groupsfound during synchronization.LDAP group names provide auto completion which will search theconfigured AD Server for groups matching the keyword. LDAP groupsthat do not exist in the AD server will result in an error message preventingupdating the configuration until a valid LDAP group is specified.



9. Complete the User Principal Mapping configuration fields as described in the table.

LDAP matches externally authenticated users to LDAP directory entries using the user's principal values. LDAP allows 0 or moremappings from a principal value type to an LDAP attribute which will be matched to identify the LDAP entry. The user principal mappingis required for SSO Kerberos use in authentication and generating a keytab file. See Establishing Security in the Vocera PlatformAdministration Guide.

In addition to the given configuration, every instance is an implicit mapping from the user's username to the login attribute configured inthe attribute mapping (using the unmodified username).

Each user is looked up in LDAP based on the requested or authenticated identity and their Vocera Platform data is updated to matchtheir LDAP data. Users are considered authorized only if they are a member of at least one of the mapped LDAP groups. Authenticationadds a step to check their password against LDAP.

User Principal Mapping Configuration Fields Description

Principal Type Select the type of principal this mapping supports from the dropdown list.A principal represents a unique identity. Options provided are NT Principal,X.509 Certificate Subject, Email Address, Kerberos Principal, or OtherPrincipal.

Active Check the Active box to enable the configuration in the Vocera Platformsystem.

LDAP Attribute Select the LDAP attribute from the dropdown list to which the principalvalue will be matched.

Regular Expression Enter the regular expression which the given principal type value mustmatch to be matched to LDAP.

LDAP Value Mapping Enter a regular expression mapping for the value to use in searching forthe principal in LDAP. A mapping of '$0' will leave the value unchanged.

10. Select one of the available options to exit the adapter configuration page. See Saving an Adapter on page 24 for details.


Synchronizing Users and Groups

Periodically the Vocera LDAP Adapter synchronizes Vocera Platform users and groups with the users and groups on the LDAP server.

The Vocera LDAP Adapter searches the LDAP server for new or changed data by default every three minutes from the time the adapter isstarted.

The first search returns all LDAP users and groups, but the following searches return only users and groups that are new or changed sincethe last search. During synchronization, new users and groups will be linked to a selected site (see Configuring a Vocera LDAP Adapteron page 8 to view Site field configuration details). Please note that existing users will not be linked to the selected site if they are alreadylinked to a different site.

When synchronizing, the LDAP Group search occurs first, followed by the LDAP Users search, then the Users are created and updated,and finally the Group memberships are updated in Vocera Platform. Users without group membership are not synchronized; they aredeactivated and cannot log into the system.

This synchronization process can be restarted without restarting the Vocera LDAP Adapter. Restarting the synchronization clears thesearch and timer, then restarts the timer and synchronization process. Depending on the number of users, this process may take asignificant amount of time because all the LDAP data is re-uploaded and processed.

Select Resynchronize Users and Groups in Additional Actions, as shown below.

Warning: The Resynchronize Users and Groups button will require a significant amount of time to process. Pressing this buttonuploads all user and group information from the LDAP server, which is then read and updated in Vocera Platform.

The synchronization initiates as shown in the message below.

An error message displays if the Vocera LDAP Adapter is not active. Restart the adapter, and allow the users and groups to besynchronized.

SYNCHRONIZING USERS AND GROUPS



Understanding Adapter Installation

Adapters are installed on the Vocera Platform in a solution package, or individually as needed by the customer.

The Vocera Platform uses adapters to integrate with external systems and devices. Each adapter is configured by the user to includeinformation that will allow the Vocera Platform to communicate and interact with a specific type of resource and, depending on the adapter,devices that resource may control. Adapters can allow the Vocera Platform to monitor and collect data, as well as send data out, whentriggered manually or automatically.

When implementing Vocera Platform at a customer site, use this document to install an adapter that is not supplied in the Gold Image.Otherwise, you will install a needed adapter when instructed in the solution package installation process described in the Vocera PlatformInstallation Guide.

Accessing Supported AdaptersSupported adapters that are not included in the solution Gold Image can be installed at a customer site.

Many Vocera Platform adapters are provided in the solution's Gold Image for installation during the customer implementation. Supportedadapters that are not included in the solution Gold Image can be installed at a customer site using the instructions provided in the Installingan Adapter on page 18 document.

The following two tables describe the set of adapters in Vocera Platform versions 5.5 and 6.0. The first table lists the adapters provided inthe Gold Image. The second table lists the optional adapters available for installation.

Adapters provided in the Gold Image

Adapter Name Platform 5.5 Platform 6.0

ascom-interface extension-ascom-interface-1.7.118-0.x86_64.rpm extension-ascom-interface-1.8.0.1.x86_64.rpm

compliancelogger-interface extension-compliance-logger-interface-1.0.103-0.x86_64.rpm

extension-compliance-logger-interface-1.1.0.7.x86_64.rpm

cucm-interface extension-cucm-interface-2.5.0-0.x86_64.rpm extension-cucm-interface-2.6.0.2.x86_64.rpm

data-export-interface extension-data-export-interface-1.4.1-0.x86_64.rpm

extension-data-export-interface-1.5.0.3.x86_64.rpm

hill-rom-clinical-interface extension-hill-rom-clinical-interface-2.0.8-0.x86_64.rpm

extension-hill-rom-clinical-interface-2.1.0.2.x86_64.rpm

hl7-interface extension-hl7-interface-1.4.5-0.x86_64.rpm extension-hl7-interface-1.5.0.2.x86_64.rpm

incoming-email-interface extension-incoming-email-interface-1.15.101-0.x86_64.rpm

extension-incoming-email-interface-1.16.0.1.x86_64.rpm

ldap-interface extension-ldap-interface-1.3.0-0.x86_64.rpm extension-ldap-interface-2.0.0.13.x86_64.rpm

media-interface extension-media-interface-1.0.105-0.x86_64.rpm extension-media-interface-1.1.0.1.x86_64.rpm

outgoing-email-interface extension-outgoing-email-interface-1.6.102-0.x86_64.rpm

extension-outgoing-email-interface-1.7.0.2.x86_64.rpm

responder-sync-interface extension-responder-sync-interface-4.0.6-0.x86_64.rpm

extension-responder-sync-interface-5.0.0.34.x86_64.rpm

spacelabs-cei-interface extension-spacelabs-cei-interface-1.0.109-0.x86_64.rpm

extension-spacelabs-cei-interface-1.1.0.5.x86_64.rpm

UNDERSTANDING ADAPTER INSTALLATION



spectralink-interface extension-spectralink-interface-2.1.103-0.x86_64.rpm

extension-spectralink-interface-2.2.0.2.x86_64.rpm

tap-interface extension-tap-interface-1.10.2-0.x86_64.rpm extension-tap-interface-1.11.0.5.x86_64.rpm

vocera-interface extension-vocera-interface-3.1.0-1.x86_64.rpm Not supported

xmpp-interface extension-xmpp-interface-3.4.2-0.x86_64.rpm extension-xmpp-interface-4.0.0.328.x86_64.rpm

Optional Adapters


amion-interface extension-amion-interface-1.0.0-0.x86_64.rpm extension-amion-interface-1.0.0-0.x86_64.rpm

assignmentgroupsync-interface extension-assignment-group-sync-service-1.0.1-0.x86_64.rpm

extension-assignment-group-sync-service-2.0.0.4.x86_64.rpm

assignmentmanager-interface extension-assignment-manager-interface-1.1.2-0.x86_64.rpm

extension-assignment-manager-interface-2.0.0.4.x86_64.rpm

carescape-interface extension-carescape-interface-1.1.108-0.x86_64.rpm

extension-carescape-interface-1.2.0.1.x86_64.rpm

earlysense-interface extension-earlysense-interface-1.0.102-0.x86_64.rpm

extension-earlysense-interface-1.1.0.2.x86_64.rpm

incomingvmi-interface extension-incoming-vmi-interface-1.0.0-1.x86_64.rpm

extension-incoming-vmi-interface-1.1.0.4.x86_64.rpm

incomingwctp-interface extension-incoming-wctp-interface-1.0.0-1.x86_64.rpm

extension-incoming-wctp-interface-1.0.0.31.x86_64.rpm

navicare-interface extension-navicare-interface-1.4.2-0.x86_64.rpm extension-navicare-interface-1.5.0.2.x86_64.rpm

nihon-kohden-interface extension-nihon-kohden-interface-1.1.102-0.x86_64.rpm

extension-nihon-kohden-interface-1.2.0.2.x86_64.rpm

outgoing-wctp-interface extension-outgoing-wctp-interface-2.0.0-2.x86_64.rpm

extension-outgoing-wctp-interface-2.0.0-2.x86_64.rpm

patient_context-service extension-patient-context-service-1.0.0-0.x86_64.rpm

Not supported

qgenda-interface extension-qgenda-interface-1.0.0-2.x86_64.rpm

sip-interface extension-sip-interface-1.4.0-0.x86_64.rpm extension-sip-interface-1.4.0-0.x86_64.rpm

soap-publisher-interface extension-soap-publisher-interface-1.0.112-0.x86_64.rpm

extension-soap-publisher-interface-1.1.0.2.x86_64.rpm

soap-subscriber-interface extension-soap-subscriber-interface-1.0.113-0.x86_64.rpm

extension-soap-subscriber-interface-1.1.0.2.x86_64.rpm

sotera-esii-interface extension-sotera-esii-interface-1.0.113-0.x86_64.rpm

extension-sotera-esii-interface-1.1.0.2.x86_64.rpm

stryker-interface extension-stryker-interface-1.0.102-0.x86_64.rpm extension-stryker-interface-1.1.0.3.x86_64.rpm

vmp-interface extension-vmp-interface-1.1.0-0.x86_64.rpm Not supported

voice-group-sync-interface extension-voice-group-sync-interface-1.0.3.12.x86_64.rpm

Not supported

Recreating a RepositoryIn the event that the repository reference file has been compromised, you can re-create the platform repository.

This information should be specified on the related adapter's Release Information page in the wiki. See Releases and navigate to theneeded adapter.

1. Verify that the adapter resides in a repository which is in '/etc/yum.repos.d/'.

2. If the repolist or yum commands fail, verify that the file exists and try again. For example, use the following code to verify the repositoryexists on the Vocera Platform appliance:

[tpx-admin@engage log]$ cat /etc/yum.repos.d/vocera.repo



3. Verify the output appears as shown.

#---------------------------------------------------------------------------------------------# NOTICE: Only use the General Availability (platform-6.X-ga) repository for customer deployments.# Use of Controlled Release (platform-6.X-cr) or Software Quality Assurance (platform-6.X-sqa) in# accordance to process QOP-75-01 Production Work Order and History Record, contact your# manager for questions. #---------------------------------------------------------------------------------------------[Platform-6.0]name=Platform-6.0baseurl=https://box.voceracommunications.com/Platform-6.0-GAenabled=1gpgcheck=0

Installing an AdapterInstall or uninstall a Vocera Platform adapter at a customer site on a Vocera system for a customer.

Execute the following steps using the system's command prompt.

1. Verify that the adapter resides in a repository which is in '/etc/yum.repos.d/'.

2. Run the following commands:

sudo yum clean allsudo yum check-updates

3. Verify that the rpm package to be installed is available using the following command:

sudo yum list available | grep extension4. Install the adapter by specifying its rpm package name in place of <package-name> in the code below. (This information should be

specified on the related Release Information page in the wiki; see Release Notes.)

sudo yum install <package-name>5. Uninstall an adapter by specifying its rpm package name in place of <package-name> in the code below. (This information should be

specified on the related Release Notes page; see Release Notes.)

sudo yum remove <package name>

Practicing an Adapter InstallationReplicate these steps using the needed adapter package, in order to install adapters other than the example given here.

1. Verify the repo file contains the repos up to and including the release of interest.

[tpx-admin@engage log]$ cat /etc/yum.repos.d/vocera.repo#---------------------------------------------------------------------------------------------# NOTICE: Only use the General Availability (platform-6.X-ga) repository for customer deployments.# Use of Controlled Release (platform-6.X-cr) or Software Quality Assurance (platform-6.X-sqa) in# accordance to process QOP-75-01 Production Work Order and History Record, contact your# manager for questions. #---------------------------------------------------------------------------------------------[Platform-6.0]name=Platform-6.0baseurl=https://box.voceracommunications.com/Platform-6.0-GAenabled=1gpgcheck=0

2. Execute the following commands:

[tpx-admin@engage log] $ sudo yum check-updatesLoaded plugins: langpacks, product-id, subscription-managerThis system is not registered to Red Hat Subscription Management. You can use subscription-manager to register. Quartz | 3.6 kB 00:00:00 (1/2): Quartz/group_gz | 483 B 00:00:00 (2/2): Quartz/primary_db | 29 kB 00:00:00

3. Verify the package is available, using the following command:

[tpx-admin@engage log] $ sudo yum list available | grep extension



extension-navicare-interface.x86_64 1.3.6-0 Platform 5.04. Install the needed adapter; in this example, install the Navicare adapter:

[tpx-admin@engage log] $ sudo yum install extension-navicare-interfaceLoaded plugins: langpacks, product-id, subscription-managerThis system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.Resolving Dependencies--> Running transaction check---> Package extension-navicare-interface.x86_64 0:1.3.6-0 will be installed--> Finished Dependency Resolution

Dependencies Resolved

============================================================================================================================================================ Package Arch Version Repository Size============================================================================================================================================================Installing: extension-navicare-interface x86_64 1.3.3-0 Quartz 59 k

Transaction Summary============================================================================================================================================================Install 1 Package

Total download size: 59 kInstalled size: 62 kIs this ok [y/d/N]: yDownloading packages:extension-navicare-interface-1.3.6-0.x86_64.rpm | 59 kB 00:00:00 Running transaction checkRunning transaction testTransaction test succeededRunning transaction Installing : extension-navicare-interface-1.3.6-0.x86_64 1/1 Verifying : extension-navicare-interface-1.3.6-0.x86_64 1/1

Installed: extension-navicare-interface.x86_64 0:1.3.6-0

Complete!5. This completes the steps to install an adapter.


Navigating the Vocera Platform Adapters

Access the Adapters tab and use the filter or search tools to display a specific adapter.

This page is used by all the adapter guides, and therefore, the adapter used as an example here may not be the adapter that you areworking with currently.

1. Access the Vocera Platform Web Console and sign in with your system credentials.

2. Select Settings > Adapters in the navigation menu.

The Adapters page displays.

3. Select an adapter to work with from the list displayed in the grid, or select the New Adapter Action option to create a new adapter.

On the Adapters page you can identify adapters by their name or component name. The Enabled column (displaying a true or falsestatus) indicates whether the adapter is active on the system, or disabled.

The bottom row of the grid reports the number of adapters displayed, of the available adapters.

The Filter Disabled box is checked by default, and displays only the enabled adapters that are configured on the Vocera Platform.

NAVIGATING THE VOCERA PLATFORM ADAPTERS


4. Uncheck the Filter Disabled box to display all the adapters that have been installed, including those that are not currently enabled. Thecolumn title now displays All Adapters.

The Filter Disabled box is checked by default.

5. Enter a term in the Search field to locate a needed adapter on the system.

The search field is identified by a text field with a magnifying glass icon. The search is performed on the Name and Component Namecolumns.

When results are returned, the column header displays Adapters Search Results and an x icon allows you to clear the search field.



Editing an AdapterEdit an adapter that has been installed on the Vocera Platform.




2. Select the adapter to edit in the Adapters list.

3. Select Edit in the adapter's menu.

The Update Adapter page for the adapter displays.

4. Edit the adapter's settings to revise the configuration as needed. See the adapter-specific configuration page for details on working withsettings for this adapter.

Select an empty field and begin typing, or select an existing value and type over it. To keep an existing value, do not edit that field.

5. Select one of the options to exit the Update Adapter page. See Saving an Adapter on page 24 for details.

Creating a New AdapterAccess the Vocera Platform Web Console to work with adapters, or create a new adapter when prompted in the package import process.






2. Select New Adapter in the Action menu on the Adapters page.

The Create a New Adapter dialog displays.

3. Complete the configuration fields.

Name Description

Component Name * Select the Component Name field dropdown arrow to display a list of the systems and devices that Voceracurrently supports. Select the name of the adapter to create.

Reference Name Enter a short descriptive name in the Reference Name field to uniquely identify an adapter instance. It maydemonstrate the adapter function or other information; for example, Production adapter may differentiate a liveadapter from a development or "sandbox" adapter.

Enabled Select the Enabled check box to allow Vocera Platform to use the new adapter. Vocera ignores the adapter ifthis option is disabled.

4. Select Upload Bundle in the Action menu to install a package on a Vocera Platform.

Use the Upload Bundle feature to install when the adapter is not available in the Component Name dropdown list, and you havedownloaded the needed adapter bundle to a storage location.

5. Click on Browse to navigate to the bundle to install.



6. Select one of the Action options to exit from the Upload a Bundle dialog.

• Upload: Upload the selected bundle to the appliance.

• Cancel: Close the Upload a Bundle dialog without making a change to the system.

Saving an AdapterClose an adapter configuration dialog using the Save, Reset, or Cancel options.


When creating a new adapter, the options at the bottom of the adapter configuration page are Save, and Cancel.

When editing an existing adapter, the options are Save, Reset, and Cancel.

Choose an option to close the dialog:

Option Description

Save Select Save to store the adapter configuration in the system, when the fieldsare set to desired specifications.

Cancel Select Cancel to close the configuration window without saving yourchanges to the system.

Reset Select Reset to clear all fields without closing the window, in order to selectother specifications for the adapter's settings.

Deactivating an AdapterTemporarily deactivate an adapter to avoid unintentional use of it in an implementation.


1. Access the Vocera Platform Web Console and navigate to the adapter to deactivate.




2. Select Edit in the Actions menu to access the Update page for the adapter.

3. Un-check the Enabled box to temporarily deactivate the adapter.

When deactivated, the Vocera system will ignore the adapter. You can easily enable or disable the adapter at any time.

4. Select one of the options to exit the Update Adapter page. See Saving an Adapter on page 24 for details.

Removing an AdapterPermanently remove an adapter from the Vocera system.


Use the remove function to permanently delete the adapter from the system. Alternatively, you can disable an adapter and the Vocerasystem will ignore it.

Warning: Remove cannot be undone. If any system features use this adapter, removing the adapter prevents the features fromfunctioning.

1. Access the Vocera Platform Web Console and navigate to the adapter to remove.


2. Select Remove in the Actions menu to permanently delete the adapter.

3. Click Ok in the confirmation window.

• Ok: Confirm the choice to remove the adapter from the system.

• Cancel: Return to the adapter page without making a change.



4. Confirm that the adapter no longer displays in the Adapters list view, when a success message displays.

vocera ldap adapter configuration guide

Documents