I'm trying to get autofill working. Specifically, either of these experiences. The former being the one I'm more interested in, but two for the sake of having more than one example.
Everything is working except the strong password generation.
I've correctly configured my AASA, I've switched everything to SSL, textContentType is correctly set, I enabled the autofill provider entitlement (after reading more I'm turning it back off though since that's not what I want (same results)). Is there something in info.plist i'm missing? I am using a keychain library to access the keychain? but I don't think that's it.
Specifically I'm trying to get to this screen
Any suggestions of where to dig would also be appreciated. At this point I'm not sure if I'm doing something wrong, or if ios12 is new and doesn't work right yet.
Relevant code? (This is all I have in the 'code', am I missing somethign somewhere else?)
pwTF.textContentType = .newPassword
pwTF.passwordRules = UITextInputPasswordRules(descriptor: "required: upper; required: lower; required: digit; max-consecutive: 2; minlength: 16;")
Do you have a UITextField that has the usernameTextField.textContentType = .username on the same page? I only got the strong password suggestion after I added the username field.
I know it may be solved already for you but here is a solution for generations to come :)
Sometimes it doesn't work cause your device have the keychain turned off.. go to Settings -> AppleID -> iCloud -> KeyChain .. and enable it .
i guess it's heuristics based and if it can't find a username field it's unhappy?
¯\_(ツ)_/¯
Related
I want to have my keys stored in System Keychain and a couple of apps(keySharing and AppGroup enabled) to access them
My current approach
I am using
let path:String = "/Library/Keychains/System.keychain"
var keychain: SecKeychain?
SecKeychainOpen(path, &keychain)
For options in SecItemAdd() ,I added
[kSecUseKeychain as String: keychain! ]
with this approach, I am able to write to System keyChain but only the current app is able to access this KeyChainItem,
kSecAttrAccessGroup
is completely ignored for this keychain item.
After some digging I found
kSecUseDataProtectionKeychain = true
is mandatory to use AccessGroup
When I included this in the options of SecAddItem(), Yes I am able to utilize access groups after this, but it is ignoring kSecUseKeychain now. Though my app is running in root and kSecUseKeychain is set, SecAddtem() is writing to login KeyChain (and apps inside my access are able to access them) instead of System Keychain
Is there a way to write to System KeyChain and allow a set of apps to modify them?
In short
[kSecUseKeychain as String: keychain! ]
is ignored when
kSecUseDataProtectionKeychain = true
Thanks
Any alternatives related to having keys in System Context is much appreciated
Xcode -12.2
macOS :10.15
I'm developing an hybrid app and I want to skip the passcode screen after having logged.
I've tried following a post about Kapsel-Logon where it is explained how to implement it, but it doesn't work for me. I don't know if the latest release makes changes null.
The file I tried to modify is:
C:\KapselSDK\plugins\logon\www\common\modules\LogonController.js
Can you help me or suggest where I wrong or what can I do/look?
yes the file that you need to change is the LogonController.js
You can find here what exactly you need to do in order to get rid the passcode screen.
Good luck!
I have downloaded the source project from
sourcecode.
I came across many issues over there, then I changed the source header path then changed the compiler version in the project settings, then all those were solved, now there is no errors, it runs, when I click FBLoginButton ,Facebook Login Dialog appeared but it looks empty,
I dont know why, The app key and app secret key were placed correctly.
I tried with device,if there would probm with simulator, still looks same.
what Im doing wrong, I had searched a lot, not found any solution, any ideas pls tell me
I have the same problem.
I have opened a bug here : https://developers.facebook.com/bugs/279606225487338
You can also vote for it, so that FB may take a look at it. Let's hope they solve it.
We had two apps in the app store which used this old api of facebook for login and they also g=have stopped working... So most probably Facebook has stopped support for this but I couldn't fond anything official. I guess we will have to incorporate the new Api.. :/ If I find something I will post here...
I'm working on a little SDK which has a configFile.plist file to store things like secret key.
Developer who implement this SDK in his app, and other users will download the app, they will be able to go into the app binary and change anything in the .plist file.
Is there any way to store this info without letting users modifing the parameters easily? I don't want users to have the ability to change the parametes in the .plist file.
Thanks in advance for any help!
When it comes to plist storage, it's easily accessible either way. Your best option is to provide a class file for configuration, and not a plist. Example below..
//Config.h
#define SHARED_SECRET #"2390849028349829384"
#define SOME_OTHER_VALUE 1
..and so on, this way, the class file is compiled with the App, and not visible to the user but accessible by the developer. Once you #import "Config.h", you can use SHARED_SECRET and SOME_OTHER_VALUE in place of the value itself within the code. If this suffices as a solution to your question, mark it as the answer. Hope it helps..
Keeping in mind that people are going to be able to see/change almost anything with the right tools, you can't prevent people from hacking this.
If the key is going to be different for each user of the SDK, then you might want to make it the Developer's responsibility and have them provide the private key to you using a delegate method. That will make it their problem, and it will make it easier for them to compile the key directly into code, which is going to be less obvious for the end-user to access.
I'm wanting to make a password unlock screen for my app, and I'm not sure how I'd go about it.
I'm wanting it to look like the Apple-designed version of it, which is the passcode lock setting screen.
How might I go about doing something like this, where as soon as all four digits are entered the code is immediately checked against a pre-set password?
Thanks!
Just found a project that replicates this perfectly. I'm going to post this here for future reference in case anyone needs it.
https://github.com/guicocoa/pinview
most likely you create the view and when all the fields are set you check against the known password or you check the hash of the input passkey against the hash you have stored.
basically you have a stored password/hash and you check against that when you have all field filled in in your view.
when the password is correct (either by hash checking or password) you show your next view, otherwise you display an error saying the password is incorrect.
Here is another library, just in case someone is looking for something like this:
http://cocoacontrols.com/platforms/ios/controls/abpadlockscreen
iOS 7 style Passcode. Complete functional demo with great documentation showing the different states (i.e Enable, Test, Change & Turn Off)
https://github.com/rolandleth/LTHPasscodeViewController