I am trying to understand how the MobileFirst Platform could prevent Jailbroken/rooted devices from accessing its resources.
Does MobileFirst Platform provide this type of security.?
How can we implement it as I could not find any resource to walk us through it?
Thanks.
MobileFirst Platform Foundation does not, in itself, provide any facility to prevent jailbroken / rooted devices from accessing resources. However, you can use MaaS360 or Trusteer to provide this kind of protection as desired.
There's a tech note here that gives an overview of mobile OS features that can be used by various versions of MobileFirst Platform Foundation and Worklight.
Related
I have to implement TeaLeaf analytics for our application so i am doing sample POc for android and iphone environment for hybrids application. Anyone please advice me how can i implement the TeaLeaf stuff in my POC.
Below that activity i did,
create sample app version project and add android/iphone environment
application-descriptor.xml i added IBM teaLeaf SDK
what else i have do? i was searching google and following ibm knowledge center also there is not much clarity for tutorial and how can i test in development environment.
below that link i referred :
http://www.ibm.com/support/knowledgecenter/SSHS8R_6.3.0/com.ibm.worklight.integ.doc/integ/t_tealeaf_client.html
If I understand your question correctly, it seems like you're attempting to create a connection between IBM MobileFirst Platform 6.3.0 and IBM Tealeaf. I work on integrations of IBM Tealeaf On-Cloud with client e-commerce platforms and it seems like you might be dealing with IBM Tealeaf On-Premise.
That being said, my understanding of the process for the On-Cloud implementation is that there are a few libraries you need to make sure are being included on pages you'd like Tealeaf to observe:
Tealeaf.js (distributed by IBM)
Sizzle.js
JQuery, if the page uses it ... also note that if the site uses JQuery, you need to provision from IBM the JQuery flavor of Tealeaf.js instead of the W3C flavor.
Hammer.js
Pako.js (again this assumes the On-Cloud version of Tealeaf, as this is a library for compressing data a being sent to IBM cloud-service collectors. In the On-Premise version my understanding is that this data is written to a file that is saved to the local hardware.)
How the libraries are included is something you'd decide when working with the client's server and development team - every organization has their preferences. Generally though they'd be inserted on pages that need to be monitored and the Tealeaf.js config would be edited to specify the endpoint of the collector for the regional data center on which space was provisioned for the client (in the US, either in Dallas or Washington DC.)
As for the On-Premise implementation of Tealeaf, you can jump in to the documentation here: http://www.ibm.com/support/knowledgecenter/SS2MBL/tealeaf_product_family_welcome.html
I have a set of applications that have been developed by IBM using MobileFirst so it uses Worklight servers and adapters within the application.
I have been requested to investigate the possibilities of taking a hybrid mobile application developed on worklight and trying to migrate it onto something like IBM's BlueMix.
I was hoping someone could provide me with some insight as to how much work may be involved or if this task is even possible?
Thanks in advance.
Assuming you are using MobileFirst Platform Foundation 7.1, you can run your MobileFirst Server on IBM Containers, a technology powered by IBM Bluemix... you can read more about it here: https://mobilefirstplatform.ibmcloud.com/tutorials/en/foundation/7.1/ibm-containers/
You can start by evaluating it: https://mobilefirstplatform.ibmcloud.com/tutorials/en/foundation/7.1/ibm-containers/evaluate/
And later, assuming you are an IBM MobileFirst Platform customer, migrate your existing project and applications to it: https://mobilefirstplatform.ibmcloud.com/tutorials/en/foundation/7.1/ibm-containers/run/
You will also want to experiment with MobileFirst Foundation 8.0 beta: https://mobilefirstplatform.ibmcloud.com/beta/
v8.0 beta also provides an all-new approach for running on Bluemix: https://mobilefirstplatform.ibmcloud.com/tutorials/en/foundation/8.0/ibm-containers/using-mobile-foundation/
Using 8.0 will require some migration effort, but it'll be worth it. :)
You could migrate your adapters and the app integrated with the MFP SDk as is and move it to Bluemix using MFP 7.1 on containers. The effort is minimal - say 2 days. Based on your comments above, If you want to ditch all that and remove worklight out of the equation all altogether, you will have to hand roll all that functionality that worklight was providing to you and of course maintain it yourself. Then this ceases to be a worklight question :) and the effort is certainly more than couple of days.
What new features are included as compared to worklight version 6.2 in MobileFirst for hybrid application? I searched a lot on google and IBM site I dont find any new things which are new in 7.1.0 for hybrid application. Can any one suggest new things which are included for hybrid app.
The biggest addition in MobileFirst Platform Foundation 7.0 was Java adapters, enabling you to write JAX-RS applications thus creating flows not possible with JavaScript adapters.
The biggest additions in MobileFirst Platform Foundation 7.1 are the introduction of the OAuth 2.0 security model and as consequence the session-independent mode in the MobileFirst Server. Also introduced were Cordova applications (as opposed to MobileFirst Studio-managed Hybrid apps), allowing more room for applicative wizardry not possible with Hybrid apps.
For an exhaustive list of changes, see the changelogs:
7.0: http://www.ibm.com/support/knowledgecenter/SSHS8R_7.0.0/com.ibm.worklight.getstart.doc/start/c_release_notes.html?lang=en
7.1: http://www.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/com.ibm.worklight.getstart.doc/start/c_release_notes.html?lang=en
Worklight 6.2: Is it possible to decommission the devices using any Worklight API apart from Licence Tracking in Worklight Server?
Not sure how an API would be of help here.
Anyway, the only available feature that allows you to disable a specific device, is the License Tracking feature you have mentioned in your question.
Feel free to submit feature requests: https://developer.ibm.com/mobilefirstplatform/help/
Is it possible to use IBM Worklight Log and Analytics feature to upload and decode obfuscated crash reports (e.g. ProGuard or the iOS alternative) to the Worklight Server?
Android ProGuard is currently not supported in Worklight (5.x - 6.2.0.x) applications, so in that respect this option is not available regardless. I am not familiar with an iOS equivalent to ProGuard.
AFAIK the Worklight Operational Analytics platform does not provide the ability to decode uploaded logs. You can however control what exactly you'd like to upload.