Repair Mac HD, Check Permissions with the OSX Startup volume. To check for disk errors and possibly fix issues with the Mac HD volume and other Partitions. Repair Permissions of the Mac HD startup volume.
![Opera Mac Asks For Permission To Access Keychain Opera Mac Asks For Permission To Access Keychain](/uploads/1/2/5/6/125610438/804898691.png)
I have an application that stores username and password in the keychain. Everything was working fine when working on Xcode 3, I recently moved to Xcode 4 and now when I run the application, I get a prompt: Application wants to use your confidential information stored in keychain' in your keychain. After hitting always allow I see the application added to access control list of the keychain item, but I get every time I run the app. Also after hitting Always allow again, I see that the access control has two instances of the same app. Seems like OS thinks this is a new application.
Any ideas appreciated. I believe the problem is that your signature's designated requirement causes it to not accept itself as 'the same app' as itself (for Keychain purposes). One common cause for this—and I think it's yours—is using a Developer ID Application cert, with no designated requirement, and without the intermediate cert installed. A standard Developer ID requirement looks like this: designated = anchor apple generic and identifier 'com.example.appName ' and ((cert leaffield.1.2.840.113635.100.6.1.9 exists) or (certificate 1field.1.2.840.113635.100.6.2.6 exists and certificate leaffield.1.2.840.113635.100.6.1.13 exists and certificate leafsubject.OU = '1AZBYCXDW9V ' )) If you want to construct this yourself, you have to replace the identifier with your bundle identifier and the subject.OU with the value from your cert. (If you double-click it in Keychain Access, it should be listed as the Organizational Unit.) Then you can add to 'Other Code Signing Flags': -requirements '=designated.'
(the whole mess from above) However, a much better way to do this is to use Xcode 4.3.2 or later. If it recognizes that you're using a Developer ID Application cert, and can see the intermediate cert in the keychain, it will generate this by default. Also, if you use the Archive Organizer in Xcode to 'Export Developer ID-signed Application', instead of just using the build from your target directory, it will make sure to sign your app and any other enclosed signables, and it will test that everything is setup properly. (The failures are pretty cryptic—e.g., your 'Choose a Developer ID to sign with' step may just have no choices, with a message in the syslog that has no useful information—but at least the fact that it failed or succeeded narrows down where your problem is.) Either way, you need to download and install (on your build machine) the intermediate cert, called 'Developer ID Certification Authority', from the 'Developer ID Intermediate Certificate' link at the site. One last thing: Even if this solves your problem running on your build machine, you really want to test on the oldest OS version you support. For example, the requirements compiled by Lion's codesign sometimes can't be parsed on Leopard, or sometimes even on Snow Leopard.
If that happens see.
Note: If you clicked on Deny by accident, follow the instructions below to restore your keychain permissions. Restore your keychain permissions for Office for Mac If the above did not work, Office may have trouble accessing the keychain and you'll need to restore keychain permissions for Office for Mac. In these cases, you may see:.
The keychain access prompt every time you launch any Office application, even though you previously selected Always Allow. A prompt to sign in to your Microsoft Account or Office 365 for business account every time you launch any Office application. An “Authentication Session Expired” error message after signing in to your Office applications. Follow these directions to restore your keychain permissions:. Quit out of all Office for Mac apps such as Word, Excel, PowerPoint, Outlook, and OneNote.
Search for 'keychain' in spotlight and launch the Keychain Access app. Select the login keychain in the left pane click the large padlock icon to lock the keychain. Note: The padlock will animate to a locked position and may take several seconds to complete if other apps are running. Launch any Office app, such as Word. You'll receive a prompt requesting permissions to access the keychain.
Enter your Mac admin account password and click Always Allow. This prompt may appear multiple times.
If prompted, sign in to your account associated with Office. Once you have successfully signed in, quit out of the application and open it again. You should be able to open the app without any more prompts.