Administration Settings

In Administration SETTINGS you can configure your shared workspace by setting properties and enabling features on the Mobile Center server.

When using the Early access features for multiple projects, some of the settings may be controlled globally by the operator. For details, see Project Management.

Configure settings

To configure administation settings:

Select a category from the left panel. After you modify the settings in a specific section, click Verify and Save and wait for the server to acknowledge your changes.

To erase the changes that you made, click Discard Changes in the top right of the screen.

Note: Some of the properties and settings are only available for Trial, Enterprise, and Ultimate license types. For details, see Mobile Center editions.

Back to top

General

This section lets you configure general settings, such as compatibility validation, lock duration (for consecutive failed logins on the account and for idle devices), and password expiration time.

The following table provides additional information regarding some of the general settings:

Enable WebSocket Security When this setting is enabled, all testing tools and integrated products connecting to Mobile Center must use an execution key for authenticating the connection. For details, see Access key management.
Password expiration

The default password expiration is 180 days. Twenty days before the expiration date, Mobile Center issues a warning to the user to change the password. A "0" value indicates no expiration date.

If a user's password expires or if a user forgets their password, an administrator can reset it from the User Management page, or scripts. For details, see Manage user accounts with scripts.

Lock duration

To prevent users from being locked out after entering a wrong password three times, set the Lock duration to "0".

Collect usage data One type of data collection is for the purpose of evaluating the usage of your lab resources. You can download CSV reports from the console containing reservation, device, app, and job information.
Single-Sign-On init string

This is mandatory for integration with the ALM extension for Mobile Center. Paste in the value of the COMMUNICATION_SECURITY_PASSPHRASE flag from the ALM Site Administration. If you leave this field empty, single sign-on will not work. For details, see Open the Mobile Center wizard.

Permission to gather data

Allow collection of data to be used interna by Micro Focus to improve the product, in accordance with the company’s privacy policy.

Limit application uploads You can limit the number of uploads for each application. This makes it easier for the administrator to manage the number of application uploads that need to be maintained, and reduces load on the file storage system.
Application upload limit When you define the maximum upload limit, older uploads exceeding the limit are deleted. If you seleced to delete old uploads of applications when upgrading the Mobile Center center, your settings will be copied over to this section.

Note that after the setting is enabled, or if the number of uploads to retain is decreased, the deletion of uploads will not be done immediately, but will be done in the background.

Back to top

Proxy setting (web access)

When using a proxy server, user this setting to configure the proxy server settings.

When using the Early access features for multiple projects, this settings is controlled globally by the operator.

Back to top

Device reservation

This section lets you set the default reservation and extension durations, in minutes. In addition, you can set the default Dev Access duration.

Android/ iOS packaging service

To enable record and replay functionality when testing certain apps, you need to repackage them with Mobile Center libraries. These sections allow you to specify the host machine, port, and protocol for the Android and iOS packagers. For details, see App packaging and signing services.

For iOS, use the Add Service button to add other packaging services in addition to the primary one. For these additional services, you also indicate the workspace that will use this service. Use the Remove button to remove packaging services that you added. You cannot remove the primary service.

Note that the Agents are always signed with the primary packaging service. For information on how to distribute the signed Agents automatically, see View and manage connectors (Admin only). This capability is only available for Trial, Ultimate, and Enterprise type licenses.

Back to top

Amazon Device Farm integration

Amazon Device Farm (ADF) integration lets you use devices from the Amazon farm for testing purposes.

In this section, you provide the AWS security credentials. If you created a project that you want to use through the EC2 interface, specify its name here.

For details, see AWS Device Farm integration or follow the links to the AWS documentation in this pane.

Note:

  • These settings override any other settings that you may have defined for your test in the EC2 instance.
  • When you disable ADF integration, the change may take up to 10 minutes to take effect.
  • AWS Device Farm integration is not supported for iOS due to ADF iOS connection restrictions. For a list of all the limitations, see the Readme.

Back to top

User permissions

As administrator, you can define permissions for users in your workspace with regard to actions on apps and devices. By default, users have permissions to perform all of the above actions.

Device actions

For devices, you can indicate whether or not non-admin users can

  • Restart a device
  • Reconnect a device
  • Remove a disconnected device
  • Change a device name
  • Change the device settings on either (or both) Android and iOS devices. When you restrict non-admin users from accessing the device Settings, the icon is displayed on the device card.

Considerations when restricting access to device settings:

Android

When the restriction is applied, the Settings app cannot be launched.

Prerequisites:

1. Remove all the accounts on the device (Settings > Account).

  • Some apps automatically add an additional account. After enabling the Mobile Center setting, check that the account has not returned.
  • On some devices, there is a setting called Users. Delete any New user items.

2. Reconnect the device.

Note that after the administration setting is enabled and the icon is displayed, you can add the accounts back.

iOS

When the restriction is applied, the Settings app can still be launched but no action can be performed on it.

iOS versions lower than 11 using the UIA test framework

Access is blocked only for replay. Manual control is not blocked. Note that the icon is still displayed.

General Note: If restricting manual control fails for some reason (for example, if the accounts were not removed from the Android device) the icon will be displayed on the device.

App actions

For apps, you can indicate whether or not non-admin users can upload an app, install an app, or delete an app.

Back to top

Network Virtualization integration

This section lets you specify the NV Test Manager machine information, its authentication token, and the protocol to use (HTTP or HTTPS).

For details about these settings, see Set up Network Virtualization integration in Mobile Center.

For information on how to set up your machine and devices, see Network Virtualization integration.

Back to top

LDAP integration

Organizations that use LDAP to manage their user accounts, can let users access Mobile Center with their LDAP credentials.

For guidelines for working with LDAP users, see LDAP users . To use secure LDAP (SSL), see Configuring Mobile Center for secure LDAP.

When using the Early access features for multiple projects, some of these settings are controlled globally by the operator.

Considerations when using LDAP:

  • When you change the Enable/Disable settings, you must restart the Mobile Center server for them to take effect.
  • If you are upgrading to Mobile Center 3.2 from a version of Mobile Center earlier than version 2.20, you must change the admin@default.com user's password before configuring the LDAP settings. Select Change Password from the user drop down in the masthead.
  • The User Search Filter setting indicates the form of the LDAP query used to find a user during login. It must include the pattern {0}, which is replaced with the user name when a user logs into the Cloud Service Management Console. If you specify CN={0}, it uses the CN to log in. If you specify mail = {0}, it uses the email.
  • When you enable or disable LDAP, all non-LDAP users, excluding admin@default.com, will be deleted.

Back to top

SAML SSO integration

Mobile Center supports single-sign on via SAML 2.0. SAML (Security Assertion Markup Language) is an XML-based standard for exchanging authentication and authorization data between an identity provider (IdP) and a service provider, such as Mobile Center. In this section of settings, you can enable single-sign on (SSO). This way, users can use one set of credentials for logging into Mobile Center, as they do for logging into other SSO applications in their organization.

Note that SAML SSO integration is currently supported for connection to Mobile Center from Appium only. UFT 14.53 Patch 1, and upcoming releases for LeanFT and TruClient will also support this.

To enable SAML SSO integration, you need to add Mobile Center to your Identity Provider (IdP). Refer to your Identity Provider documentation for instructions on how to configure your IdP for a new SAML 2.0 application. You will need information (metadata) about Mobile Center when configuring your IdP. Download this by clicking the DOWNLOAD Mobile Center METADATA link.

You will also need to add the following information from your IdP to Mobile Center, so that SAML-based authentication requests can be sent to your IdP:

IdP SAML metadata

This can be a URL, or you can copy and paste the contents of the IdP metadata .xml file into this field.

Administrator login name

This is a user, defined in the IdP, that will granted Mobile Center administrator permissions. Initially, only this user will be able to access the Administration menu to perform administation tasks such as configuring settings, and managing workspaces, licenses, and access keys. The administrator can assign admin permissions to additonal users by changing the user role in Administration > Settings > Users. For details, see User management.

Username attribute identifier

User attributes are information used to identify individual users. In this field, provide the SAML attribute name for the username attribute that the IdP uses for identification on sign in. Depending on how you configured your IdP, the username attribute for signing in can be an email address, or a unique user name.

Tip: You can find the attribute identifier in the AttributeStatement section of the IdP SAML response. Look for the SAML attribute name with a value that equals the attribute that IdP uses for identification on sign in.

For example, if email address is used for authentication of users against the IdP, the identifier in the example below is http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress

Alternatively, use {$id} to take the username from the subject of the SAML assertion, and not from Attribute section.

Authorized users List the names of the users, as defined in the Identify Provider (IdP), who are authorized to access Mobile Center. If the field is left empty, all users defined in the IdP will be able to access Mobile Center.

After you have successfully defined the SSO settings, or if you update any of the settings, you will be prompted to log out and to log in again using your organization credentials. If you disable SAML SSO, you will need to use your Mobile Center credentials to log in again.

Note: When you enable or disable the SSO setting, all existing users, excluding admin@default.com, will be deleted.

If you enabled SSO but cannot log in to Mobile Center as an administrator, for example, if you wrongly configured the administrator user, you can disable SAML SSO by running the User management script.

Back to top

Mobile Center hosted device lab integration

This section lets you enable integration with a Mobile Center hosted device lab and specify the Oauth2 credentials needed to access the devices.

Micro Focus provides you with the access key when you purchase your Mobile Center hosted devices contract.

Back to top

Genymotion integration

This section lets you specify the GMTool path to allow integration with Genymotion cloud devices. For details, see Genymotion cloud integration.

Back to top

Service Virtualization (SV) integration

This section lets you enable Micro Focus ervice Virtualization (SV) instrumentation when uploading apps.

This integration allows you to virtualize you sensors, APIs, and devices. For details, see Service Virtualization integration.

Back to top

See also: