AppsAnywhere Cloud Deployment Guide
Introduction
Welcome to your Deployment Guide for AppsAnywhere.
The aim of this document is to gather the details that AppsAnywhere will need to configure a new AppsAnywhere instance.
This article only applies to AppsAnywhere Cloud deployments.
Contacting AppsAnywhere
If at any stage you cannot find the information you need or have any questions, please reach out via GuideCX or AppsAnywhere Support.
Our dedicated team are also available to help you throughout this process and we can arrange further support calls as needed.
Prerequisites
To complete onboarding, the following information will be required.
Network File Share
Please read the following articles to configure a precache location for How to Configure and Use Pre-caching on Managed Devices.
If the share is hosted in Azure, please ensure the share is created and access granted according to https://docs.microsoft.com/en-us/azure/storage/files/storage-files-quick-create-use-windows.
See the following for more information:
Network File Share Checklist
Please update the table with the file share path.
Usage | Network Location | Sizing |
Precache files | \\filestore.uni.edu\AppsAnywhere\Precache | 100GB |
Please confirm:
Item | Details | Completed |
Permissions | Granted for the required users and groups | |
Storage | 100GB allocated |
Identity Provider (IDP) Configuration
A SAML identity provider will be used to provide authenticated access and single sign on (SSO) to the AppsAnywhere instance. To configure authentication, read:
IDP Checklist
The following information is required to perform the initial first stage configuration:
Property | Value |
IDP Metadata URL or XML file | e.g. https://login.microsoftonline.com/xxxxxxxxx/federationmetadata/2007-06/federationmetadata.xml |
SAML attribute name containing username value |
SAML Attribute Provisioning information
SAML attributes retrieved when a user authenticates form the basis of the filtering process used to display which relevant applications that you have provisioned can be consumed by that user. To configure mapping, read:
Attribute checklist
To create and configure mappings, the following information is required:
Attribute Name | Expected filter value |
e.g. http://schemas.microsoft.com/ws/2008/06/identity/claims/groups | xxxxxxxx-8025-xxxx-a342-xxxxxxxx6fde |
The filtering logic used by AppsAnywhere, each individual attribute defined uses OR logic (any matching value). When multiple attributes are defined in the same filter, AND logic is used, so all the individual attribute definitions must return true for the filter rule to be positive.
AppsAnywhere Directory User
For the AppsAnywhere team to install, administer and access AppsAnywhere, a directory account is needed.
Username | appsanywhere |
Usage |
|
Password Policy |
|
Please confirm:
Item | Details | Completed |
Credentials | Provided securely |
Administrative User accounts
To manage the applications and delivery methods within AppsAnywhere, privileged user accounts will be created for each person requiring access.
Details of the available roles are available on User Roles and Permissions.
Account checklist
Please provide the user account information and required role(s):
Username | Email address | Role(s) required |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Create a CNAME (optional)
It is recommended to use the AppsAnywhere URL provided (e.g. https://uni.appsanywhere.online).
To use a custom domain name in the AppsAnywhere URL (e.g. https://appsanywhere.uni.edu), prepare the relevant team within your organization to create an entry in your local DNS server.
A member of the AppsAnywhere team will provide the URL that needs to be redirected during the AppsAnywhere product handover.
SSL Certificate
This is only required when using a custom domain name for the URL.
If required, create and provide the SSL certificate to be applied to AppsAnywhere by following SSL Certificates.
This certificate should be used for the service provider sections of SAML SSO configuration.
SSL Certificate Checklist
Please update the table with the download location of the certificate .pfx file.
Please confirm:
Item | Details | Completed |
Password | Provided securely |
Handover to AppsAnywhere
Please review the details to ensure all information has been provided to the AppsAnywhere team.
Next steps
Provide the details securely and directly in GuideCX.
Mark the GuideCX Task as Done
Once AppsAnywhere is ready for handover, a member of the AppsAnywhere team will be in touch.
Kind Regards
AppsAnywhere Implementations