I'm working on a project where employees will receive Chromebooks. The plan is to use the native Office 365 Android Apps.
The Chromebooks are configured to authenticate against Azure AD which is configured by using this document:
https://learn.microsoft.com/en-us/azure/active-directory/saas-apps/google-apps-tutorial
Everything works like it should and I can SSO to the Office 365 portal (portal.office.com) and use all my Office 365 apps.
However, I would like this to work for the Android apps as well, e.g. if the user starts Excel for Android, to have it SSO sign-in as well.
The problem is here that the user account also exists in Google and it uses that account to access the Play Store and Android apps, not the Azure AD account.
Any idea how to accomplish this or is this just plain impossible?
Thanks!
There does not seem to be any official documentation on this. However, my experience from my Android phone and Chromebook is that there is SSO between the Office365 apps even if it doesn't SSO from the initial Chromebook login. So they may need to sign into one of the apps, but from there the login will transfer between them. That login is also good for a period of time based on your O365 policies.
What that means for your users is that during initial setup they may need to log in twice- once for the Chromebook and once for the Android apps. After that they will only need to log in once to the Chromebook and occassionaly refresh their credentials for the apps.
Related
We noticed in the Office 365 login page, users are asked to enter work, school or personal Microsoft accounts. As an enterprise work account based app, we don’t want users to complete sign in with outlook.com or other personal Microsoft ids.
I’ve seen in iOS apps like Groups iOS using ADAL that take people to login page that allows only work or school account. Entering an outlook.com says its not supported.
Can we do this in Android maybe with a query param or similar? I couldn’t find this config in the Github readme
Simply add queryParam
msafed=0
Use this in the
AuthenticationContext.acquireToken()
parameters
I'm building an app for both Android and iOS. Users should be able to login but I don't want to deal with their passwords myself and want to use third party sign-in. I already implemented Google sign-in on Android (https://developers.google.com/identity/sign-in/android/start-integrating) and iOS but since I'm not sure how many iPhone users have a Google account I was wondering whether there is an Apple alternative. Can I use the Apple ID or maybe iCloud account for this purpose?
I am trying to test a Facebook Ads Management application, for advertising for mobile apps specifically. I don't have a real mobile app but need a mobile app registered on facebook and in ios and android app stores in order to reference its facebook app id when testing ad creation. Is there a way to have a mobile app like this, just for testing purposes?
I registered a MobileTest app on Facebook, but I don't have a mobile app in the stores for the Facebook app to point to.
if you are just testing you can use any other apps available on app store (google play or ios). If you are just checking the functionality or your Code then its a good option. We also don't have any mobile app so we used other play store apps to publish ads (didn't run those ads). Use any app which has fewer downloads.
I was using Facebook login and other 3rd Party login in mobile game based on the way that,
client integrates Native Facebook SDK (or other native sdk)
client login and get OAuth access token
client pass access token to server side and server makes a server-side authentication to Facebook
if server side get FB Uid, then based on it creates an account or login to existing account for the user.
My question is, in order to free user from login to service every time, is it possible to directly use Apple ID on the device for such flow of authentication? What about Android and Google ID? Or other type of solutions I should look into?
I know the question is old, but it's one of the first that get get listed when searching for "apple oauth"...
Apple has anounced at the WWDC 2019 a new feature called Sign in with Apple which allows you to use oauth for apple logins like facebook, twitter, google etc. Developer resources can be found here and a good introduction here.
————- update: ————————————————
We now have Sign-In with Apple: https://developer.apple.com/sign-in-with-apple/
—————— old version —————————————
For apple user accounts there is no oAuth 'ID'-provider
https://discussions.apple.com/thread/6594633?start=0&tstart=0
https://en.m.wikipedia.org/wiki/List_of_OAuth_providers
My personal opinion about that fact is the following.
Apple wants to sell hardware. If software is needed to support that, they implement or buy it.
Apple might be wrong, as web apps are integrating Facebook, Google, Twitter, Windows Live and sometimes Weibo, LinkedIn or Amazon oAuth.
I never heard about plans for oAuth for Apple ID.
I'm designing an API for an Android app. An iPhone requires a user to get an Apple ID, do Android mobile devices in the same way 'require' users to get a Google ID?
Ideally I want to be able to assume that users downloading our app on Android will have a Google account, so that we authentication via the Users and OAuth APIs is a snap.
You're not required to have a Google account associated with an Android device, though most people probably do. You do need one if you download apps through the Market, but you can also side-load apps, use other markets like the Amazon App Store, etc.
For both the Android phones that I've bought in the US (an HTC G1 and an HTC G2) it has forced me to enter my Google account information (or create a new Google account), before I could do anything on the device (similar to how the iPad forces you to connect it to iTunes before you can use it).
Some people suggest clearing the data associated with all the Google apps on the phone to disconnect the device from the Google account, or you can just remove the account through Settings -> Accounts & Sync.
I suspect it boils down to exactly how the carrier delivers the phone to users. If you want your app to be available globally then you should assume many users will NOT have a Google account.
Generally, users need a Google ID to use Android Market. As far as I know, they do not need one to use other markets (such as Amazon). What are you authenticating?