Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
This is a follow up to this question.
If I’m going to store a user’s username and password with Keychain Services, should I simply create my own prompt view with an NSSecureTextField for the password, and then once the user enters their info pass it to a Keychain Services API (I found this one)?
I’m concerned Apple won’t like me interacting with a users sensitive data directly like that.
It appears that the only way use a user’s password for Apple’s Autoingest tool is to handle the password directly in code. I make sure to not hold onto it longer than I need it, and of course I store it with Keychain Services in order to keep it secure.