Murray Brown
asked on
Access 2010 - Package and Sign - No certificate available
Hi
In Access 2010 I am trying to distribute my database application
using File >> Save and Publish >> Package and Sign
but
I get the message "No certificate available - No certificates meet the application"
What do I do to remedy this?
In Access 2010 I am trying to distribute my database application
using File >> Save and Publish >> Package and Sign
but
I get the message "No certificate available - No certificates meet the application"
What do I do to remedy this?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The only thing the signing does is ensure that the package that is received by your enduser is the same as the package that came off your machine.
Who would you be shipping this to?
Who would you be shipping this to?
ASKER
Great answers. Thanks
I asked who you're shipping to so that we could further provide assistance, however:
If you're shipping this to endusers who are NOT on your domain (i.e. clients, customers - anyone not at your place of development), then you cannot use the self-certificate with any reliability. You can ship the entire certificate (including the keys and such) to the end users and have them install, but in general that is not something clients/customers feel comfortable doing (since this results in lots of ominious warnings about security and such).
The point being: If you're shipping this to endusers, I wouldn't consider going the self-certificate route. PUrchase a code-signing certificate, as suggested earlier, and use that.
If you're shipping this to endusers who are NOT on your domain (i.e. clients, customers - anyone not at your place of development), then you cannot use the self-certificate with any reliability. You can ship the entire certificate (including the keys and such) to the end users and have them install, but in general that is not something clients/customers feel comfortable doing (since this results in lots of ominious warnings about security and such).
The point being: If you're shipping this to endusers, I wouldn't consider going the self-certificate route. PUrchase a code-signing certificate, as suggested earlier, and use that.
ASKER
Thanks LSM
Please check out a further question that I have asked where you can elaborate:
https://www.experts-exchange.com/questions/26747611/Access-can-I-ship-an-application-to-end-users-using-the-Self-Certificate-built-into-Office.html
Please check out a further question that I have asked where you can elaborate:
https://www.experts-exchange.com/questions/26747611/Access-can-I-ship-an-application-to-end-users-using-the-Self-Certificate-built-into-Office.html
Only putting the database into trusted location will eliminate the messages.
I can't say whether this is by design or not, but digitally signing an A2010 app is pretty much a waste of time.