Hello,
i am running Froyo on my nexus one.
When configuring a new Exchange support, i get:
""SETUP COULD NOT FINISH.
This server requires security features your phone does not support""
Touchdown is working fine and reports the following securities features:
Allow simple password
Password/PIN required
Failed attempts 10
Min length 5
Min Complex 3
Timeout 1800 sec.
Password recovery
So the question are:
1) Which of this securities is not yet implemented natively in froyo?
2) Will it make it in the final froyo release?
If any of you has some inputs, it would be nice to share.
Thanks in advance!
Best
dico
Sorry I cannot help with your problem other than to say that I have exactly the same issue. I am really shocked that Google have not got this fully working. We are hardly talking about a new protocol here!
Whilst I have Touchdown and have done since moving to Android last year, this single problem has stopped my company giving everyone Android phones. Come on Google, get it sorted!
Maybe because the foryo we got is not final? Ever thought of a unfinisched product that you use, is not finisched?
jaapschaap said:
Maybe because the foryo we got is not final? Ever thought of a unfinisched product that you use, is not finisched?
Click to expand...
Click to collapse
I think the point is that proper exchange support should really have been there from day one.
You just don't build a serious, high end smart phone with out proper integration to corporate mail (read exchange ).
Unless you're Google apparently.
badomen said:
I think the point is that proper exchange support should really have been there from day one.
You just don't build a serious, high end smart phone with out proper integration to corporate mail (read exchange ).
Unless you're Google apparently.
Click to expand...
Click to collapse
Well, I work and live in the corporate world and use my phone as such a device. I guess I sort of agree with you there about the exchange support, I can't really legitimize why they didn't incorporate this almost-brainless sync method.
Does the security policy of your works exchange server require to have a screen lock pin, specifically mobile device security policies? I noticed, after wiping from Froyo(with screen lock pin prior to EX acct) to CM and then back to Froyo(no screen lock when configuring), that I received an error that setup could not finish, I assume this is because without having a screen lock policy set up on the phone the exchange server will not authenticate to my device. Check that out. Also, this is not a finalized product.
Mine works fine...and I manage the Exchange system here...no problems.
My biggest issue is that Google has provided half-ass support for Exchange, and this version is no different.
You can't even move an item to another folder from the inbox with the stock Froyo.
The Desire Rom has the functionality and ability, best interface and options compared to the stock Android.
The stock Rom sucks honestly...if it weren't for Desire...I would still have my iPhone, even they figured out, licensed and got working properly the Exchange support 18 months ago. Windows mobile devices have had this for 3-4yrs.
My first post! May as well make it contributory.
It is interested to note that one may need a PIN lock set up first *before* adding an exchange account that requires one... I know I haven't been able to get our 2.2 Nexus One's to connect to our corporate Exchange Server for my girlfriend and I.
Let me go change to a PIN lock and see what happens when I try to add the exchange account...
Yep, no go still. "Unable to open connection to server."
They really need to add a Verbose button to these error messages.
still not working
Hello,
I tried setting up a PIN code before starting up the email application.
Does someone knows where to find the email app log file to see what is not good?
Thanks in advance!
best
CJ
To be honest, I tried using touchdown (which as great as it is, still lacks a lot of features), then tried using the Froyo Email/Calendar apps... Nothing has ever worked smoothly with Exchange + Android. I ended up migrating my email server (luckly it is only a personal email server) to Google Apps, and I have never been so happy with the performance and stability.
It is a tough cookie to swallow, but gmail is much better then Exchange on Android...
Anyone know if there is a way to disable the lock pattern/pin in FROYO when you connect to an exchange server that requires it? I know about Lock 2.0, No Lock and Flyscreen but those are just overlays and wont disable the built in lock.
When I was running the Desire Rom there was a trigger you could set up on the table that held that flag but I'm sure that was a SenseUI thing.
I did search but found a ton of threads on the apps listed about but nothing to disable the built in lock.
aad4321 said:
I dont have that with exchage for me. It probably from the exchange sever and cannot be over ridden I know that blackberrys do that as well.
Click to expand...
Click to collapse
Your exchange server admin must not that set up that security feature. My work has it set up. It was able to be overwritten but FROYO changed some APIs and that doesn't work any more. I'm hoping someone has found another way to do it but after I Google it, it doesn't look like it.
aad4321 said:
I dont have that with exchage for me. It probably from the exchange sever and cannot be over ridden I know that blackberrys do that as well.
Click to expand...
Click to collapse
Of course it can be overridden. If you have root you control the phone and the rest is just software. Here ya go
http://forum.xda-developers.com/showthread.php?t=655649
Hey all. I tried syncing my university outlook account to my phone and the server requested literally FULL CONTROL over the device. I'm talking everything from camera functions to having the ability to erase my phones data.
Naturally, this poses as somewhat of a threat to me but I really need that account on my device. Does anyone know how to revoke the outlook server's administrative rights, perhaps via app ops?
QUICK UPDATE: it's asking me to encrypt my phone or else the native email app which I synced it to will not run. Can anyone stop this as well?
Sent from my SM-G900A using XDA Free mobile app
abraxo said:
Hey all. I tried syncing my university outlook account to my phone and the server requested literally FULL CONTROL over the device. I'm talking everything from camera functions to having the ability to erase my phones data.
Naturally, this poses as somewhat of a threat to me but I really need that account on my device. Does anyone know how to revoke the outlook server's administrative rights, perhaps via app ops?
QUICK UPDATE: it's asking me to encrypt my phone or else the native email app which I synced it to will not run. Can anyone stop this as well?
Sent from my SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
these policies are set by the university exchange administrators and can be over-wrote by mods (However, i highly recomend against it, some mods just aren't worth the security holes they create) I know it sounds like big brother taking over but it is the responsibility of the exchange admin to maintain security control over the exchange environment. if you were to remove the security and something detrimental happened i.e. the U got hacked and it was traced back to your account well the results would be not in your favor.
that being said the control and requirements are granular to an extent your exchange admin should remove the ability to control any aspect of your device except the specific email account you are reffering to.
cstayton said:
these policies are set by the university exchange administrators and can be over-wrote by mods (However, i highly recomend against it, some mods just aren't worth the security holes they create) I know it sounds like big brother taking over but it is the responsibility of the exchange admin to maintain security control over the exchange environment. if you were to remove the security and something detrimental happened i.e. the U got hacked and it was traced back to your account well the results would be not in your favor.
that being said the control and requirements are granular to an extent your exchange admin should remove the ability to control any aspect of your device except the specific email account you are reffering to.
Click to expand...
Click to collapse
But would you say it is worth encrypting the device? Way I see it, there isn't too big of a difference between a pass code and encryption except for the fact that you can't undo the latter without a factory reset. Is there a way to at least bypass that or do you recommend going through with the device encryption anyway?
Sent from my SM-G900A using XDA Free mobile app
abraxo said:
But would you say it is worth encrypting the device? Way I see it, there isn't too big of a difference between a pass code and encryption except for the fact that you can't undo the latter without a factory reset. Is there a way to at least bypass that or do you recommend going through with the device encryption anyway?
Sent from my SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
are they requiring device encryption or email encryption? the law firm where i work requires that all email on the device be encrypted but do not enforce device encryption.
My personal opinion is im fine with the email encryption but when they tell me my whole device requires it thats where they cross the line, access to my email is not that crucial that im willing to encrypt my whole device.
ultimately the decision is yours.
I'd like to add my corporate email to my head unit. On my tablet, it requires security to be enabled with a pin. I don't want that on my head unit. Any way around it? I want to be able to use everything else in the radio, and I'm thinking its best not to add it?
Thanks!
There are two apps in the market you can use - Touchdown or Nine (I prefer nine)
It satisfies the PIN requirement by forcing you to type in your pin only when you open the app - not on the entire device.
It does let you read part of incoming messages in notification without requiring pin at all.
As far as I know there is no simple way to completely remove the pin
Hooch0903 said:
On my tablet, it requires security to be enabled with a pin. I don't want that on my head unit.
Click to expand...
Click to collapse
Depends. Do you want to keep your job? The Android email app is simply enforcing a corporate policy. You would likely be violating your company's policy if you bypass it.
I'll have to ask if they'll approve it, since I can't add the radio to the server without their approval anyway. Appreciate the input...guess we'll see what they say about it.
Sent from my iPhone using Tapatalk
Make sure you put 1* reviews on your Banking apps or all apps that need updating to support face unlock, hopefully it will help speed up the development and support of face unlock on the pixel 4. I am really missing fingerprint unlock on my apps!
Demolition49 said:
Make sure you put 1* reviews on your Banking apps or all apps that need updating to support face unlock, hopefully it will help speed up the development and support of face unlock on the pixel 4. I am really missing fingerprint unlock on my apps!
Click to expand...
Click to collapse
Why? I just contacted my credit union asking for them to add support. Maybe larger national banks and stuff should have been aware and had support ready but smaller, more local institutions might just need to know that it's a thing on Android now.
Sent from my Pixel 4 XL using XDA Labs
In the Play Store, you can reach out to contact each app's development team via email. I've written to Chase, Bank of America, Mint, Credit Karma, and the other apps I use. Some developers are aware that they need to update, others aren't. Here are some of the responses I've received.
My original email (to each app):
Please update the Android app to support the biometric API so that I can use the secure face unlock on my Pixel 4! Thank you!
Click to expand...
Click to collapse
Bank of America:
Thank you for your feedback and we apologize for the inconvenience. We are working to update to the latest biometric authentication for the Pixel 4 and expect to have a supporting app shortly. For now, sign-in to the app using your online ID and password. Please look out for an app update soon.
Click to expand...
Click to collapse
Chase:
We'll be happy to review your request to update the
Android App.
Ivan, please note that the Chase Mobile App will work on
any Android smart phone or tablet running Android
operating system 5.0 (Lollipop) or higher. The minimum
operating system is 5.0 or higher. If your mobile phone
does not have the minimum requirement, the Chase Mobile
app will not be compatible.
We want our mobile app users to have the best experience
possible, so we regularly test chase.com using the most
current versions of operating systems. Since some mobile
app functionality may not work well on older operating
systems, we ask that you perform these updates. We
recommend you update your operating system and application
to the newest versions available. If your device isn't set
up to receive updates automatically, you can get the We
recommend you update your operating system and application
to the newest versions available.
We appreciate your business and thank you for choosing
Chase.
Click to expand...
Click to collapse
Credit Karma:
To determine if your Touch ID or Face ID function is turned on or off, go into your settings by clicking the icon in the top right corner of the app. The directions are the same whether you’re using Touch ID or Face ID.
If Touch or Face ID is turned on you will see a green circle with a white check mark.
If it’s turned off, simply click the empty circle and you’ll be prompted with a message stating the fingerprints or face registered on your phone can be used to access your Credit Karma account. Click “OK” to this prompt and you will be asked to enter your PIN to confirm this change.
Touch or Face ID is now turned on and you will be allowed to use this function to access the Credit Karma app moving forward.
Please note that if you log out of your account, the next time you open the app you’ll be prompted to enter your email address and password.
Thanks so much,
Click to expand...
Click to collapse
I've been sending further follow-ups to the ones who clearly don't understand what we are asking.
The more people who contact them, the more they'll understand that their apps are the problem by not using the current API.
I think Chase already stated that they were going to have an update before the end of the year. Hopefully sooner rather than later.
Robinhood works!
btonetbone said:
In the Play Store, you can reach out to contact each app's development team via email. I've written to Chase, Bank of America, Mint, Credit Karma, and the other apps I use. Some developers are aware that they need to update, others aren't. Here are some of the responses I've received.
My original email (to each app):
Bank of America:
Chase:
Credit Karma:
I've been sending further follow-ups to the ones who clearly don't understand what we are asking.
The more people who contact them, the more they'll understand that their apps are the problem by not using the current API.
Click to expand...
Click to collapse
Very nice work, I have left reviews and also contacted all my Banks via email. Hopefully it speeds up the process.
Throwing up a bunch of one-star reviews won't help, and all it serves to do is make the rater (you) look petty and childish. I'll send an email to my institutions, like a grownup, and go from there.
Getting in contact directly works best, via the play store will get you to the android app devs. I usually go through Twitter and you get a spokesperson who wouldn't know an apk from an adb and will give a stock response of soon™.
Remind them that the old biometric APIs are deprecated and that they should update to current versioning. Should anything happen they don't want to be the story of the bank that wasn't able to keep up.
Honestly I'm not missing it that much for my bank that much because I use LastPass which autofills it quickly. I do miss it for Outlook though because I have to do a pin.
Sent from my Pixel 4 XL using Tapatalk
So Far E-Trade has been updated to the Pixels face Unlock... I sent an email via the app store also to a credit union hoping they will update their app. I'm hoping within the next 2 weeks to a month that all major banks will update...
How secure if this anyway? I mean, my banking account has a password. I enter that password in my banking app to log into my account. In the future I will use my facial scan to log into my banking app.
Does that mean my banking account will have two password (1x password + 1x facial scan) oder will my password be stored somewhere in the app or on android and simply be passed on the my facial scan is verified?
Both do not sound very secure to me.
If you don't feel it's secure then just don't use the app.. simple. I trust that the banks know the risks and have mitigated them. After all they are the ones on the hook if there's fraud.
bobby janow said:
If you don't feel it's secure then just don't use the app.. simple. I trust that the banks know the risks and have mitigated them. After all they are the ones on the hook if there's fraud.
Click to expand...
Click to collapse
Not really the informative answer I was looking for.
I wouldn't blindly trust a bank app or any of the other countless apps that would use my facial scan.
What happens if your facial scan gets stolen / leaked. Everyone with that information will for ever be able to access your data. And you can't even change your access code like you would be able to with a password.
And it seems like you also have no idea where your facial scan is being saved, and how it is secured / locked down. Maybe it is just a plain file on your phone's storage? You don't seem to know.
Why no simply write down all your passwords in a .txt file and save it on your sdcard? That would alteast have the advantage that you could change your password at some point.
Utini said:
Not really the informative answer I was looking for.
I wouldn't blindly trust a bank app or any of the other countless apps that would use my facial scan.
What happens if your facial scan gets stolen / leaked. Everyone with that information will for ever be able to access your data. And you can't even change your access code like you would be able to with a password.
Click to expand...
Click to collapse
Isn't the face unlock for that device only? It's not like someone can install your bank app on their phone, somehow use your face unlock information, and spoof you on that device. Also there's still 2 step verification, at least with my bank, so the new app would still need to get the verification code. If anything, it's easier to do with your password because that's something that can be typed in and then somehow get the verification code text.
Sent from my Pixel 4 XL using Tapatalk
Utini said:
Not really the informative answer I was looking for.
I wouldn't blindly trust a bank app or any of the other countless apps that would use my facial scan.
What happens if your facial scan gets stolen / leaked. Everyone with that information will for ever be able to access your data. And you can't even change your access code like you would be able to with a password.
Click to expand...
Click to collapse
I'm not sure of the question you are asking. It seemed rhetorical to me basically commenting on how you don't think fingerprint, facial or password entry is secure on your app. I don't think any of it is stored in the cloud but nonetheless it's probably not as secure as walking into your bank and transacting with a teller. Even websites probably aren't as secure as you wish they were. So what exactly are you asking that you expect a reply to? You can perhaps check with your bank as to what your liability would be if your account got hacked.
EeZeEpEe said:
Isn't the face unlock for that device only? It's not like someone can install your bank app on their phone, somehow use your face unlock information, and spoof you on that device. Also there's still 2 step verification, at least with my bank, so the new app would still need to get the verification code. If anything, it's easier to do with your password because that's something that can be typed in and then somehow get the verification code text.
Sent from my Pixel 4 XL using Tapatalk
Click to expand...
Click to collapse
Oh is it? That makes it defeniately more secure. But then I would still like to know how it is ensured that my facial scan only works with my specific mobile device and not with any other mobile device.
Yep for banking there is still 2 step verficiation. Good point. But I was actually thinking more about e.g. KeePass.
bobby janow said:
I'm not sure of the question you are asking. It seemed rhetorical to me basically commenting on how you don't think fingerprint, facial or password entry is secure on your app. I don't think any of it is stored in the cloud but nonetheless it's probably not as secure as walking into your bank and transacting with a teller. Even websites probably aren't as secure as you wish they were. So what exactly are you asking that you expect a reply to? You can perhaps check with your bank as to what your liability would be if your account got hacked.
Click to expand...
Click to collapse
Maybe I didn't explain my question good enough. I will try again:
Currently I would unlock e.g. my KeePass Database with a password.
In the future I would use my facial scan for that.
I wonder at what point my facial scan will access my password of the KeePass Database, because it somehow has to know my password in order to unlock KeePass?
And in that case my password suddenly isn't saved only in my head anymore but also within android or another app (because Face Unlock has to somehow know it?).
Or will my KeePass database get a second "password" which is my facial scan data?
In that case I want to make sure that my facial scan is very secure and can't be stolen. Because if it turns up in smth like "haveibeenpwnd.com" everyone will forever be able to access all my files with my leaked facial scan which I cannot even change to something different anymore.
Utini said:
Maybe I didn't explain my question good enough. I will try again:
Currently I would unlock e.g. my KeePass Database with a password.
In the future I would use my facial scan for that.
I wonder at what point my facial scan will access my password of the KeePass Database, because it somehow has to know my password in order to unlock KeePass?
And in that case my password suddenly isn't saved only in my head anymore but also within android or another app (because Face Unlock has to somehow know it?).
Or will my KeePass database get a second "password" which is my facial scan data?
In that case I want to make sure that my facial scan is very secure and can't be stolen. Because if it turns up in smth like "haveibeenpwnd.com" everyone will forever be able to access all my files with my leaked facial scan which I cannot even change to something different anymore.
Click to expand...
Click to collapse
I used LastPass and I think it's not different then when I died the fingerprint option for it. There's a master password for the account and biometric login is, again, just for the individual device. And again, there's 2 step verification at least with LastPass, for whenever you set up.
Sent from my Pixel 4 XL using Tapatalk
EeZeEpEe said:
I used LastPass and I think it's not different then when I died the fingerprint option for it. There's a master password for the account and biometric login is, again, just for the individual device. And again, there's 2 step verification at least with LastPass, for whenever you set up.
Sent from my Pixel 4 XL using Tapatalk
Click to expand...
Click to collapse
Sounds interesting and secure. Now I am interested in how it is ensured that my fingerprint / facial scan will only work with my specific mobile device and that the stolen data from my device can't be used from another device
Utini said:
Oh is it? That makes it defeniately more secure. But then I would still like to know how it is ensured that my facial scan only works with my specific mobile device and not with any other mobile device.
Yep for banking there is still 2 step verficiation. Good point. But I was actually thinking more about e.g. KeePass.
Maybe I didn't explain my question good enough. I will try again:
Currently I would unlock e.g. my KeePass Database with a password.
In the future I would use my facial scan for that.
I wonder at what point my facial scan will access my password of the KeePass Database, because it somehow has to know my password in order to unlock KeePass?
And in that case my password suddenly isn't saved only in my head anymore but also within android or another app (because Face Unlock has to somehow know it?).
Or will my KeePass database get a second "password" which is my facial scan data?
In that case I want to make sure that my facial scan is very secure and can't be stolen. Because if it turns up in smth like "haveibeenpwnd.com" everyone will forever be able to access all my files with my leaked facial scan which I cannot even change to something different anymore.
Click to expand...
Click to collapse
Oh I see now. This really has more to do with your password manager than the bank. Unfortunately, I don't use a PM even though I suppose I should. Everyone says it's pretty secure. Since I don't really know what I'm talking about at this point I'll give it a shot anyway. lol
I don't think the facial scan or the fingerprint scan is saved anywhere other than your device. But I do use fingerprint (or did) scans on my banking app. If I change my password on the banking site my fingerprint scan will no longer work on the app. I would first have to change my password on the app and then reregister my fingerprint when the new password is entered. Can we compare it to the face scan at this point? I mean you can't change your fingerprints either right? Before I go on, am I reading your concerns correctly?
Utini said:
Sounds interesting and secure. Now I am interested in how it is ensured that my fingerprint / facial scan will only work with my specific mobile device and that the stolen data from my device can't be used from another device
Click to expand...
Click to collapse
https://support.google.com/pixelphone/answer/9517039?hl=en
Maybe this confirms it?View attachment 4860867
Sent from my Pixel 4 XL using Tapatalk