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.
Related
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.
I am trying to set up a custom SAML Web app with auto provisioning in my google admin. I am able to create an custom SAML Web app but the auto provisioning feature is not available. As per this community link there are a bunch of other apps which provide auto provisioning. I couldn’t find a way to setup a custom one.
I am creating a custom SAML Web app by following steps:
Logging into google admin
App -> Web and Mobile Apps -> Add App -> Add custom SAML App
Below is how it looks after i create few apps already present in the apps list and when i create a custom SAML App. The custom app clearly does not have the User auto provisioning or there is a setting for the same which i am missing.
How do i set up auto provisioning for custom SAML Web app?
Please help!
Currently there is no support for auto-provisioning on custom SAML apps. In their release blog post Google explains how this works:
Following this launch, admins will be able to set up automated user provisioning and deprovisioning for Salesforce.com and other apps (with support for more applications coming soon).
These are apps that they are specifically adding support to. Since then they have been steadily adding more apps to their catalog, but it's still a predefined list. All SPs have different APIs to provision users so it is probably not so easy to create an interface that will be able to connect with any of them, so Google seems to be sticking to implementing them one by one.
The link that you shared contains another link to Apps that support automated provisioning, which has the full list of supported apps. Any app outside of this list won't have auto-provisioning available.
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?
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.
I'm designing an iPhone/android app which needs user to login using his/her facebook account.
The app uses GAE (Google App Engine) as the background server, so the problem now is that I don't know how GAE, iPhone and Facebook authentication works.
My guess is user login FB from iPhone and will get an access_token, and then the iphone app sends the access_token to GAE so that GAE can recognize the user.
Is that correct? Or is there any tutorial about how to cooperate between these platforms?
Thanks!
Take a look at the LeanEngine open source project. It was designed to do exactly what you are trying to do - login from a mobile device to GAE with Facebook or OpenID account (and sync data between the client and GAE).
It consists of a preprogrammed GAE application and libraries for Android and iOS and if you are satisfied with the built-in functionality you really do not need to do any modifications to the server part. You can just use it as it is.