IBM Support

Passwords @ MaaS360

How To


Summary

MaaS360 prioritizes password management for device and data security. From Container Pins to Device Passcodes, each password serves a unique purpose. MaaS360 manages specific passwords, while others require provider involvement. Effective password management enhances security and functionality within the MaaS360 ecosystem.

Steps

MaaS360 Container Pin
If you ever forget your Container Pin, you can conveniently reset it using the 'Forgot Pin' button on the bottom of the PIN Prompt. Use the password that aligns with authentication method found on the User Record, such as Local, Corporate, or Azure authentication. This method ensures that your Users have a reliable way to regain access while maintaining container security.  To set up your Container Pin, you can utilize the Workplace Persona Policy. This policy helps you establish a strong Container Pin to enhance the protection of your content. Disabling the Container Pin does not automatically remove the previously set pin. If you wish to remove the Container Pin completely, you can contact MaaS360 support for assistance. Requesting this feature removal will result in the removal of the pin upon next entry.
Device Passcode
In case you forget your passcode, you can reset it if your device is online and has been unlocked recently. Locate the Device in your MaaS360 Inventory and select, More > Reset Passcode. However, that KME (Knox Mobile Enrollment) devices have an exception to this rule. You cannot set a universal passcode for all devices. Each device requires its own unique passcode for enhanced security. It's important to understand that taking action to remove the passcode on an iOS device does remove the code. The user has one hour to set a new code before force the user to create one.  However, on Android devices, when the Administrator sets a new code in the portal, it must also adhere to the policy requirements for security purposes.  Additionally, it's important to be aware that when disabled the passcode policy does not automatically remove the passcode that was previously set on the device. This method ensures that even if the policy is disabled, your device remains protected by the passcode you have configured.

Mail
While MaaS360 streamlines the mail configuration by sending server settings, Users will need to provide their mail account's password during the setup process. It's crucial to keep this password secure to maintain the privacy and security of their mail account. If you ever need to update the mail account settings or change the password, users will need to directly contact your mail provider to make the necessary adjustments. Any changes made should be reflected on your Policy to ensure continued access. 

Enrollment Password
Make sure to check the "Override Method" option before proceeding with enrollment. Failure to do so will result in the User's Method being followed instead.  For One Time Passwords (OTP) and MaaS360 Local Passwords, you can rely on MaaS360 to manage them efficiently. Keep in mind that MaaS360 Local Passwords have an expiration period of 90 days, while OTP passwords expire after a default duration of one week.  However, for all other passwords, it's necessary to go through your provider for management and updates. To troubleshoot any potential issues during enrollment, it's recommended to check the Cloud Extender or the Azure Integration settings. Ensuring that these configurations are correct will contribute to a smooth and successful enrollment process for your devices.

Portal Login
MaaS360 offers flexibility through various authentication methods, including MaaS360 Local, IBMid, and Corporate login options. When logging into the portal, administrators must use the appropriate link that corresponds to their chosen authentication method.  In case an administrator encounters login issues or needs to reset their password, it's advisable to reach out to their respective provider for assistance. For example, if using IBMid, administrators should follow the recommended steps to reset their password or address any login-related concerns.  By selecting the correct authentication method and maintaining communication with the relevant provider, administrators can effectively manage their portal logins and ensure seamless access to the MaaS360 platform.

Service Accounts
Service accounts play a crucial role in various integrations within MaaS360. These accounts are essential for ensuring seamless functionality across different services. However, some service accounts may not have a non-expired password, which can potentially lead to synchronization issues down the line.  Managing the passwords for service accounts is vital to maintaining the integrity of these integrations. It's essential to remember that MaaS360 does not have the capability to reset or manage these passwords. Therefore, to avoid any disruptions in sync or integration processes, service account passwords must be managed directly through the respective provider.  By proactively managing and maintaining the passwords for service accounts, you can ensure the smooth operation of integrations within MaaS360 and prevent any potential issues arising from expired or incorrect passwords.

Policy Password
These passwords are required to access specific features or settings outlined in the policies. For instance, passwords can be set for actions like connecting to WiFi networks or exiting Kiosk Mode on devices.  It's important to understand that policy passwords cannot be reset externally; they must be managed directly through the policy settings. When configuring these passwords, it's worth noting that read-only administrators will not have the ability to view the password details within the policy.

Factory Reset and Activation Password
Some devices may require a password to ensure that only authorized individuals can activate or reset the device. GoogleApple, and Microsoft all offer features to set up these passwords for added security.  While MaaS360 has the capability to assist with managing these passwords, they are primarily handled by the respective device manufacturers and providers. If you encounter any issues related to device activation, it's recommended to reach out to the device manufacturer for guidance. In cases where a device cannot be activated due to previous actions being locked to the device, contacting the manufacturer becomes crucial to resolve the issue.

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB24","label":"Security Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYSXX","label":"IBM MaaS360"},"ARM Category":[{"code":"a8m3p000000hCH9AAM","label":"PLATFORM"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

Document Information

Modified date:
06 October 2023

UID

ibm17029250