Your account does not have permission to create Developer ID Application certificates - xcode

Can anyone help me with the following error message?
I have seen a few of these messages in Xcode (and on Stackoverflow) but not exactly this one. I have an admin role (but I am not the account holder). Does anyone know why Xcode has problems with the creation of the Developer ID Application certificate?
In Xcode I signed in with the admin account but still no success. Any help is highly appreciated!

The documentation on this is pretty clear from this chart (see https://developer.apple.com/support/roles/):
You are not the account holder so you do not have the ability to create Developer ID certificates. The Account Holder must create them. The certificate belongs to the team as a whole so you will be able to use it.

Related

App Store Connect Allow Developer Resources Checkbox When Adding User

I am trying to add a User to my App Store Connect so they can upload a build, but in the portal it does not allow me to give them access to certificates as the checkbox stays greyed out. I am the Account holder and Admin. "Access
to Certificates, Identifiers & Profiles" stays grey. Cant change this even when added as a User and try to edit their permissions.
This is probably because you have an individual account instead of organization one. I found it here.
Hope this helps anyone like me who got stuck here.

Can not create new application

I am unable to create a new application in the Square Developer portal. It just says that an error has occurred but there isn't any indication of what the error is or how to correct it.
Finally found out what to do. When setting up my developer account it seems that Square does not differentiate between a developer who wants to make their code work and a customer who wants to use their services. Once I had linked my bank account to the merchant account I was able to create the application.
But... I don't want a merchant account, I'm just developing the code.

Unable to revoke Mac Certificates

I was having some code signing problems and in a rash decision I decided to delete all my certificates and private keys and to start over. I read and understood that this would mean a lot of work to set things up again, but I didn't think this would create an irreversible situation:
I have 10 un-revokable Developer ID certificates: 5 Developer ID Application certificates and 5 Developer ID Installer certificates, with different expiration dates (2017 to 2019).
If I click the + button to add a certificate the radio button for Developer ID is unselectable (grayed out).
So, my problem is that I don't have the private key for these certificates, I can't revoke them, and I can't create new Developer ID certificates. One other thing: I'm the only member of the team.
I called Apple Developer Support and they weren't sure how to fix this. They said they'd have to get back to me.
Anyone else have any suggestions?
Thanks
Philip
Okay, in case anyone else missed this in the App Distribution Guide here's what I found:
You can’t revoke Developer ID or Passbook certificates using Member
Center. Instead, send a request to Apple at product-security#apple.com
to revoke these types of certificates. If Apple revokes your
Developer ID certificate, users can no longer install applications
that have been signed with that certificate. Instead of revoking a
Developer ID certificate, you can create additional Developer ID
certificates using Member Center as described in “Requesting
Additional Developer ID Certificates.
I didn't realize 5 Developer ID Application and 5 Developer ID Installer certificates were the limit. Hopefully, Apple will revoke them for me.
I got some extra certificates also (5). It took about two weeks and various emails to and back from Apple support, but I got them in the end.
Its very important when creating your new certificate using KeyChain to immediately backup the private and public keys that are created with your name when you do the "Request a Certificate from a Certificate Authority" stage within the KeyChain app. This will enable you (hopefully anyways) to re-use your developer id certificates when you change machine.
I deleted all private and public keys in my name (again using the KeyChain app) prior to doing this step so to reduce confusion but that may not be necessary and might even be unadvisable.

How to create an organisation account on chrome web store?

I have searched a lot about this on web but found nothing relevant. I want to publish chrome extension on web store on behalf of my organisation. My organisation uses Google apps. But I cant see any option to publish in chrome webs store even after logging into my organisation account on google. Please help
May be you have googled with wrong set of token words. Please check the link below:
https://developers.google.com/chrome/web-store/docs/publish. Here you can get all the relevant information. A developer account is to be created. Then you can login to the developer dashboard and publish your app or extension. Still, if you find it difficult, please let me know.

Diference between Certificates in "Login" and "System" for XCode

I try to found answer for this stupid question, but didn't find it. I am having the error CSSMERR_TP_NOT_TRUSTED and I am trying to fix it.
My question is: What difference make put a "Certificates" in "Login" or in "System" in the "KeyChains" tab of "KeyChains Access" program? Is a good idea copy and paste all certificates in this 2 places?
Say things like: Certificates in Login is for use in login, and in system for system isn't the answer. :)
The System keychain is for System wide items. So if you were to have an identity for you laptop, that would be in your System keychain. Every user has access to it as well, so it's a good place for things like SSL certificates. It also takes admin credentials modify it.
On the flip side, you are the only person who can access your login keychain. It's actually locked with your account password. This is where your Apple Developer certificates should go. They are specific to you and identify a person, not a machine. Another big plus is that applications can request access to it without having admin credentials.

Resources