This guide describes the first steps in getting started with CapaInstaller Self Service.
It outlines how to install, set up authentication and create the first configuration for devices and users.
Follow the below steps to install the CapaInstaller Self Service Portal
Deploy a Back-end Service
To be able to communicate with CapaInstaller services and to authenticate against an Active Directory, the Self Service Portal relies on the CapaInstaller Back-end Service.
If you already have a Back-end Service Deployed for other purposes, skip this step.
To save time and effort, mark and copy the Back-end service public url to the clipboard. You will need to enter this URL later when installing the Self Service Portal.
- How to Deploy the Back-end Service
Enable the Web Server
- IIS 7.5 or above
- .NET 4.5.1 or above
Enable the Web Server (IIS) role on the Windows Server that is set to host the Self Service Portal site. This server's DNS name will be the base URL for access to the Self Service Portal.
Execute the Windows Installer package
Execute the Windows Installer package (CapaInstaller Self Service Portal.msi) for the Self Service Portal.
Locate the file in the share of the root configuration management point e.g. "...\CMPDEV\Resources\Self Service Portal\CapaInstaller Self Service Portal.msi"
Follow the steps in the guided Setup and enter the URL to the relevant Back-end service, when asked.
Setting up IIS
Self Service Portal use SSL port 9443
Ip address: All Unassigned
Host name: (nothing)
SSL certificate: wildcard cert
Setting up access
To enable automatic access for devices and users without the need for login/password the below options should be configured
There are two methods of granting access to Self Service Configurations. One requires credentials and the other a specific link distributed as a Webclip on the relevant devices.
- Users will get access to a Self Service Configuration when they are linked to it. This can either be a direct link to a single user or by linking the Self Service Configuration to a group containing users.
- The user can manage the content of the Self Service Configuration on the devices where he/she is the primary user.
- The content is limited by BU and the type of device. If the device being managed is in a BU, content that is in other BUs, can not be installed.
- Access to the Self Service Portal without specifying credentials can be enabled/disabled in Options > System Administration > Self Service.
- Devices that are linked to one or more Self Service Configurations, will then be manageable in the Self Service Portal if specified in the url. This can either be a direct link to a device or through a group with devices.
- When a Device is given access to a Self Service Configuration, a link is sent to the device, which will open the Self Service Portal for that specific device.
- The URL will contain the device token of the device, so anyone with access to the url/device token will be able to manage that device from ANY device.
User access and device access can be combined to give access to both the device specified in the url and the user's primary devices.
Specify the URL
- Specify the url for the Self Service Portal
Enabling Device Acess with token in options
- In the top menu select Tools -> Options -> System Administration,
- Expand the Self Service section
- Select "Allow Access to Self Service Protal with token and without credentials"
Set up authentication link distribution.
To distribute and maintain the correct authentication links, a replicator must be assigned to the global task "Manage Self Service" and a Schedule for this task created.
- Select the Global Tasks button in the toolbar
- Right click the Manage Self Service task in the list.
- Assign a replicator
- Create a schedule
Adding a Self Service Configuration
Locate Self Service Configurations in Groups > System Groups in Configuration Management
Click on Create
- Enter a name for the configuration
- Select the applications that will be available via this configuration
The Self Service configuration is now ready. Users and devices can now be linked to the configuration using the buffer.
Content can be linked directly to a Self Service Configuration and consists of mobile applications. Content can not be linked through groups.
A Business Unit Self Service Configuration, can only contain content which is in the same Business Unit as it self.
A Global Self Service Configuration can contain all content.