I want to implement OAuth in Worklight 6.2. I searched the internet and couldn't find any document related to this. Please help me with the document required to implement in Worklight 6.2.
There is no built-in OAuth support in Worklight 6.2.
The steps to integrate such support are detailed in the following article, written for Worklight 6.1, but suitable for 6.2 as well
Connect IBM Worklight hybrid mobile apps to LinkedIn services using OAuth
This article demonstrates doing so for LinkedIn, so you will need to adjust it accordingly for your use case.
Related
we have working MobileFirst 6.3 javascript adapters on our app and authentication is based on the setActiveUser and getActiveUser of the WL.Server APIs.
Which is the equivalent in MobileFirst 8? I see that there is the UserAuthenticationSecurityCheck, but available only on java Adapters..
Thank you
In MobileFirst Foundation 8.0 authentication flows are implemented using security checks, and security checks are only Java adapters. There is no equivalent for this in JavaScript adapters for v8.0.
I recommend that you will read through the following topics to learn more about migrating to v8.0:
Authentication and security: https://mobilefirstplatform.ibmcloud.com/tutorials/en/foundation/8.0/authentication-and-security/
Migrating applications: https://mobilefirstplatform.ibmcloud.com/tutorials/en/foundation/8.0/upgrading/
I've published a native android application which uses a services with response in JSON format. Now, I want to develop a Hybrid application using IBM Mobile first platform. I want to use the same service here in this case also. I'm not able to findout the mechanism to do so. Anyone please suggest me some solution.
I assume that you intend to build your hybrid app using HTML, CSS and JavaScript.
You could directly call the service using standard JavaScript
XMLHttpRequest(serviceUrl)
But you probably will use some framework such as AngularJS - such frameworks really do pay off in the long run - and in which case you have nice APIs
$http.get(serviceUrl).then(doSomeWork);
However this raw JavaScript approach does not exploit the MobileFirst programming model. We tend to find that using a Mobile Gateway architectural pattern, where MobileFirst adapters act as the gateway, pays off as your application becomes more complex. The adapters provide a security model and can implement aggregation and filtering so that precious mobile bandwidth is used more efficiently.
Hence we recommend that you build adapters, as described in the links given by Idan, and then you use the MobileFirst API to call the adapters:
WL.Client.invokeProcedure( ... );
Starting MobileFirst Platform Foundation 7.0, both the JS framework (for Hybrid apps) and the Native SDK (for iOS and Android) provide REST support. You can accomplish this using either JavaScript adapters or Java adapters.
Read the following tutorials explaining how to use MFP adapters:
Server-side development
If you're interested in Java adapters as well, take a look at these videos as well:
Getting familiar with IBM MobileFirst Platform Foundation Java Adapters [Part 1]
Getting familiar with IBM MobileFirst Platform Foundation Java Adapters [Part 2]
We are exploring IBM Mobilefirst capabilities with a mapping application. We are using Esri ArcGIS Mapping service.
Where can I find the available resources or sample tutorial to use Esri ArcGIS with IBM MobileFirst hybrid applications?
Not every available tool out there has guides for IBM Worklight/MobileFirst.
It looks like Esri ArcgGIS has a developer website.
You should start there: https://developers.arcgis.com/en/sign-up/?origin=developer
Read how to integrate it into applications.
If there are SDKs then you will need to integrate those like you would any other SDK - that is outside of the Worklight/MFP scope (the integration).
I would assume that if it an SDK, you could then add a Cordova plug-in that would allow you to access that SDK from your app, or even better you could use the Send Action feature to bridge between Web and Native and vice versa.
Adding native functionality to hybrid applications with Apache Cordova
Action Sender
we are working on a hybrid application targeting iOS and Android using IBM Worklight 6.1 - Developer Edition. We have to support accessibility. Any pointers, how to support it in hybrid applications, like what attributes to add, any libraries to add, or any inbuilt api that can be used, etc. I know how to provide accessibility support for native apps but am pretty new in hybrid front.
Thanks
So what you're talking about is accessibility in a Web environment. The way it is done for the Web should be mostly done in the Hybrid as well app with adjustments.
So I would google for accessibility in HTML5, for example:
https://www.google.co.il/search?q=html5+accessibility&oq=html5+accessibility&aqs=chrome..69i57j0l5.3895j0j1&sourceid=chrome&es_sm=91&ie=UTF-8
There is also a topic about Accessibility in the IBM Worklight Information Center:
Developing accessible applications
I am building an iOS and Android Apps using Worklight Framework, the worklight server will be protected by IBM Security Access Manager (ISAM) SSO, and therefore the Apps can only be reaching the worklight server after passing the Security challenges. I've found some docs about this integration and it works as intended.
But the apps also offers some features that doesn't required login, in which the Security Manager shouldn't intercept the adapter request to worklight server. The only workaround that suggested by IBM is to create a URL mapping junction in ISAM that defines the URLs that can access by public, and those which shall not. for example /worklight/public and /worklight/secured
But the URL pattern for all worklight adapter are /worklight/invoke?adapter=ADAPTER_NAME, so do we have a way to create a customized URL for public and secured adapter, for example:
/worklight/public/invoke
/worklight/secued/invoke
EDIT 1: Worklight Version 6.0
Thanks in advance.
Please mention the version of Worklight you are using.
One way to achieve this is to create and deploy the adapters in two different projects. That way the context root of both the adapters will be different. So, you'll have URLs such as
/Project1/invoke?... and Project2/invoke?... which you can apply to your filters.