I have created an app using IOT boilerplate in IBM Bluemix and added a devices as described in http://www.ibm.com/developerworks/cloud/library/cl-mqtt-bluemix-iot-node-red-app/.
I have following queries
Is there a way I can retrieve devices information (Authentication Token, Organization ID) from my Android app. As at present, after creating the devices I need to fill this information manually in my Android app which may not be feasible in real life scenario.
Is there a way I can create this device on IBM Bluemix from Android App.
Regards,
Sengar
You can register a new device via the HTTP API. With this your android app can register it's self and will be given the required tokens to log into the service.
Related
I wasn't having such a problem when using the old Firebase authentication methods. After accepting Identity Platform, my gmail and phone auth systems are not working in "android release" mode of my app (downloaded play store app). I'm currently search of the reason for this. I also put the sha keys to Firebase from Google Console App Signing and i also debugging authentication code base with test phone numbers and test gmails. There is no problem in code base or sha keys(my opinion). Now I am verifying oauth in Google Cloud Console. When this verification is verified, will my gmail and phone auths in android release mode be opened? And how long does this verification process take? Ios gmail and phone auth methods work well in the apple store or emulator. Also when i look at Google Cloud Console there are some errors on Identity Toolkit Api and Token Service Api.[enter image description here](https://i.stack.imgur.com/BeF3a.png)
I think the cause of the problem is identity platform integration and this validation for oauth. For what other reason do you think the firebase authentication systems (gmail and phone) works on iOS but not on Android?
I am developing an application using Supabase, Flutter and Google OAuth and I would like to know if it is possible to have a single clientId and clientSecret for each device type (ios, android and web) so that I don't have to implement a different authentication workflow for each device.
I have tried looking around the Google Console and see if it is possible to create a single authentication API for multiple devices. I also tried searching online.
There are sevral types of Oauth2 clients.
installed app client (for applications run on the machine)
web app clients (for applications run on web servers)
Android app clients (for applications run on android devices)
IOS app clients (for applications run on Iosdevices)
The authorization method for these three types is different, the code used to authorize them is also different. They can not be mixed.
Android app requires SHA-1 certificate fingerprint
Ios app requires App Store ID
web app requires a redirect uri
So the answer is no you can not create one type of credential to work with Android, Ios and web, you need three different credential types.
a bit of sdk magic
If a user authorizes your web app, they may not need to authorize your android and Ios apps as long as the credentials are all part of the same project on Google developer console.
Last I checked this is not true the other way around, if a user authorizes android or ios first and then tries web they will need to authorize again.
My guess is this is something baked into the android and ios sdk on googles side that is not part of the respective client libraries for web. Either that or its something in the authorization code grant that isn't in the mobile code grant type for Oauth2 I have never bothered to dig to far into it.
My requirement is to be able to embed the devices I purchase through aws device farm inside my website. The devices will have our mobile app installed in it, and the users would be able to interact with the application via the web.
We have other controls also on our website which directly control the actions in the app, which is why we cannot give the app to the user directly.
Does aws device farm provide that facility?
How to fetch device information (Google Advertising Id or IDFA) from a progressive web app
https://developers.google.com/web/progressive-web-apps/
Google Advertising ID is not accessible to progressive web app running in browser and so the installed PWA.
Said that, you can make it available to your installed PWA using an Android service(which is a native code getting the Google Advertising ID) and passing it to your PWA using Deep links, by setting a Indent filter to your PWA with a URL and have the ID retrieved in your native code passed to web app in the query para (URL).
You can refer to this java code to retrieve device identifiers and wrap it as a Android service, which calls your PWA using deep links.
We want to deploy App Center Client (maybe to customize one based on App Center API) as other apps developed based on MobileFirst platform. The current environment has LDAP (TDS) and ISAM (TAM), how to implement the SSO between them?
I know we can easily to do SSO between common mobile apps based on MobileFirst Platform, but if we want add the appcenter client to SSO, how to do it?
Device SSO between MFP-based applications is indeed possible.
A requirement for Device SSO to work isa connection to the MFP Server
The Application Center installer app is a MFP-based application as well, however this application does not contact the MFP Server. It contacts the Application Center Management Server.
So in theory, you could enable device SSO by following the user documentation (linked above), however it will be "one-sided" in the sense that it will work in the Application Center installer app only if the login was first done by the "regular" MFP-baed app.