KMS Go Admin FAQs

Printer-friendly version
Audience / Tech Expertise: 

Q: KMS requires that you have forcehttps enabled. Does your entire MediaSpace instance have to be over https?

A: Kaltura no longer requires forceHttps in versions KMS 5 and above. Your SSL settings should be set with a minimum of Login Only (or All Site). 

 

Q: Is MDM supported?

A: KMS Go can be delivered as an IPA (for iOS) file. This file is compatible with numerous MDM's.
Please contact your MDM provider and find out if an IPA file can work for you.

 

Q: How long does the authenticated session last for a logged-in user?

A: An authenticated session lasts as per the mobileSessionLifeTime configuration in the Kmsapi Admin Configuration. 

When a KMS server deploys a new version to production, the previous session expires.

Q: SAML security -  Are the login credentials cached and encrypted?

A: KMS Go does not cache user data. A session cookie is maintained in the app after a user logged in, using NSUerDefaults, without encryption.

All data is stored in NSUsersDefaults in the app/kms-instance settings, and in the user's cookie if logged-in.

 

Q: Does the app connect to ADFS system each time it is launched?

A: No, KMS Go uses the session configured to access the MediaSpace server.

 

Q: When does a user have to re-enter their ID and Password?

A: When a session expires, which depends on the MediaSpace Kmsapi module configuration for the mobileSessionLifeTime.

 

Q: Will the KMS Go app work on On-Prem Platform?

A: If your On-Prem version contains the Kmsapi module the KMS Go app should be configurable. However, you must have the latest Kmsapi module for the app to work, Contact your Kaltura customer reprenstative for information about updating the Kmsapi module.

 

 

FAQ Type: 
(1338 reads)