Security

This post is referring to Vahana 2 (beta version). To check the document for production, please go to vDesigner-v1.0

Security is one of the important modules of Vahana Cloud. It allows you to build the security access policies for the application that you design in vDesigner. Before publishing a mobile app, you need to define the access policies. 

While defining the access policy for an application, you can define several session related timeframes, requirements of app related logs.

You can define the access policies as follows:

  1. On the Application dashboard, click on “Security” on the left panel.

2. You now land on the “Security” section.

The values of the policies are pre-filled. However, you can edit the values as required.

Policy Description
AP_STATUSEnter ACTIVE/INACTIVE in this field to set the status of the application.
AP_CLIENT_SECRETThis is a prefilled field which you can edit to connect to the Vahana Run Time Manager.
AP_SERVER_LOG_REQUIREDEnter Y/N in this field denoting Yes/No, if you require server audit logs for reporting purposes.
AP_APP_SESSION_EXPIRY_TIMEIn this field, enter the value in the day unit. This value specifies the number of days after which the mobile app session will automatically expire. If the app session expires, the user needs to restart the mobile app by tapping its icon.
AP_USER_SESSION_EXPIRY_TIMEIn this field, enter the value in the minute unit (For example: – 1440). This value specifies the timeframe after which the users login session in mobile app will automatically expire.
AP_MULTIPLE_SESSION_ALLOWEDEnter Y/N in this field denoting Yes/No to allow multiple sessions on the mobile app. Allowing multiple sessions on the app specifies that more than one user can access the app by using different devices.
AP_INACTIVE_SESSION_REQUIREDEnter Y/N in this field denoting Yes/No to if you want to define the user inactive session expiry time.
AP_INACTIVE_SESSION_EXPIRY_TIMEIn this field, enter the inactive session expiry time. The user inactive session time specifies the timeframe, in which the user does not perform any function on the mobile app. 

After the user is inactive longer than the configured value of user inactive session expiry time, the user session will automatically expire on the mobile app. Therefore, the user will have to log in the mobile app again to access it.
AP_MOBILE_APPLICATION_LOGS_REQUIREDEnter Y/N in this field denoting Yes/No, if you require communication logs of mobile app.
Was this article helpful?
YesNo