EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB36410: New enhancement by Mobile 9.x: Confidential Authentication Mode.


Community Admin

• Strategy


New enhancement by Mobile 9.x: Confidential Authentication Mode.

Starting with Mobile 9.0.2 HF2 Patch 1, Administrators can set projects to be confidential, which will require users to log onto the application at start up or after a period of inactivity. User credentials are validated against the server while online and against locally cached (encrypted) credentials while offline.
 
This feature works for the following authentication mode:

  • Standard
  • LDAP
  • Database Authentication

 
The confidential project authentication mode configuration consists of two settings, one at the device level and one at the project level.
 
The device level setting is the timeout that will be used to determine when the user must be authenticated.
 

ka04W00000148t7QAA_0EM440000002APy.jpeg

 
The project level setting indicates which projects are confidential.
The project level setting is a check box under each project definition. The confidential project
authentication mode will take effect when there’s at least one project marked as confidential.
 
 
The confidential project authentication will only prompt for the credentials of the first
confidential project, so it’s required that all confidential projects use the default project
credentials.
 

ka04W00000148t7QAA_0EM440000002APs.jpeg

 
Login will be prompted when the following scenario occurs

  1. App is opened for the first time since the device is unlocked
  2. App has been turned off (not running in the background) and re-open regardless of timeout
  3. The idle timeout is reached

 

ka04W00000148t7QAA_0EM440000002APu.jpeg

 
 
 
 
 


Comment

0 comments

Details

Knowledge Article

Published:

June 14, 2017

Last Updated:

June 14, 2017