It's possible using the Mutual authentication feature which allows you to setup certificates for users so they are authenticated via a certificate instead of a username/password. Please note that this is not enabled by default in your org and you need to raise a case to get it.
The steps involved are
Contact salesforce.com to have mutual authentication ...
You may like to watch following video.
AppBuilder Transition Certification focus on declarative skills. It do not focus on Visualforce at all now. It do focus on Lightning Introduction, Salesforce1 understanding, Sandbox and Packages.
Platform Developer 1 focus on coding skills. It also focus on ...
Finally got the right way!, same certificates can be installed across sandboxes with the the below steps:
On the source sandbox
Security Controls -> Certificate and Key Management
Click on Export to Keystore
Provide a Keystore password
Click on export
A file Java Keystore format with extension .jks (e.g.
will get downloaded to local ...
Rename current certificate, then create a new self-signed certificate with a previous name. This way you won't need to update your code references, but might still need to update configuration (single sign on and/or API client certificate).
You can find these under Security Controls > Certificate and Key Management.
My understanding is that it will not impact apps built using the Mobile SDK 3.0 as it already supports SHA-256 in its libraries. However, you still need devices/ browsers meet the compatibility criteria for SHA-256.
You can find more details here.
The error SunCertPathBuilderException is given when the certificate you are using for your server is not configured correctly.
This could be for a number of reasons. If you're site is accessible to the public, I'd recommend checking the servers SSL configuration with one (or both) of the following online tools:
SSL Server Test
DigiCert® SSL Installation ...
Many services do not support 4096-bit keys. A web search came across So you're making an RSA key for an SSL certificate. What key size do you use?, where the author explains the primary differences between the two.
It basically comes down to speed, security, and compatibility. Many platforms are not compatible with 4096-bit keys, using 4096-bit keys will ...
Developer 401 is succeeded by App Builder. Developer 501 is succeeded by two exams namely Platform Developer 1 and Platform Developer 2.
If you hold Developer 401, you can take a transition exam and get the App Builder certification.
If you hold Developer 501, you can take transition exams of Platform Developer 1 and 2.
Hope it clarifies your confusion.
To put in simple terms Self Signed Certificates are like false drivers licence .It provides security to a certain level but can be easily hacked but its still better than having nothing .Check this excellent article
Now why the certificates expired message exists is a mystery and there is a good blog with some research but its still a mystery but no harmful ...
Steven Lawrence from Salesforce answered me on November 14 about this, at the Salesforce Success Community Group about Salesforce Infrastructure. His answer was:
Fortunately, this change does not affect calls to
PageReference.getContentAsPDF() or PageReference.getContent() when the
PageReference object is for another resource within the org, such as
I think the second problem you listed is causing the first problem, and unfortunately it's a bit of a layered answer. I'm also assuming that the MetadataService layer you've generated is all correct.
The first part to solve is getting the ConnectedAppOauthConfig.isAdminApproved = true. Now I couldn't get this to set on creation of the Connected App. However,...
How a mainstream encryption scenario works in SAML: identity provider encrypts some elements of the SAML response with service provider's public key. (I am assuming an asymmetric cipher which is how most implementations incl. Salesforce do this). The service provider decrypts using the private key that corresponds to the public key used to encrypt. In other ...
I was able to figure out the issue. There were two reasons for this error.
Certificate was not signed by one of the 100+ Salesforce trusted CA.
Intermediate certificates were not installed on the client's server.
Once they fixed these two issues, I was able to successfully ping the server.
Following is the link you can use to check if the endpoint ...
Self-signed certificates are for applications with no public domain name that cannot be accessed outside a local or VPN network. CA certificates should be used for applications with a public domain name and must be secured.
For example, your SSO solution using AD FS most likely used a self-signed certificate. Your public web portal with a public SSO feature ...
I believe the problem is different. In salesforce you can talk to only those servers which includes digital certificates which are signed by Certificate Authorities to which salesforce trusts.
Here certificate authority for your endpoint- https://apps.daikinapplied.com/McQuayToolsSrvc/Authentication.asmx
is "Kaspersky Antivirus Personal Root Certificate". ...
The Dev 401 certification doesn't test any of the Apex and Visualforce skills but the name says a Certified Force.com Developer. So now salesforce made the changes to this developer certification so that the Platform developer I certification test basic knowledge on Apex,Visualforce,Lightning. Where as the configuration skills is certified as Platform App ...
I know Salesforce supports at least some of the digicert root certificates as I have implemented this in production. I have blogged a 5-part article series on setting up two-way SSL authentication with Salesforce and you can find it here. Though this article deals with Salesforce and IBM Websphere Cast Iron, the technique and most of the steps applies to any ...
You can do it:
Custom Domains: Using an Existing HTTPS Certificate With Your Community
It is possible to request a new HTTPS certificate or to reuse certain existing certificates in your community domain. Broadly, there are two options:
If your community will need a new HTTPS ...
The steps above seem to be incomplete: I tried to delete the old certificate and it said it was still being used. Here is my take:
Email Warning: Sandbox: SFDC Expiring Certificate Notification
If you get an email with the following Subject Line, follow the instructions below: Note: The instructions in this link seem to be incomplete. How to renew ...
It is because Application Architect is earned upon completion of other certifications:
Salesforce Certified Application Architect For those who assess
functional requirements from a declarative viewpoint.
Certified Data Architecture and Management Designer
Certified Sharing and Visibility Designer
Certified Platform Developer I
Certification maintenance requirements are documented by Trailhead:
Keep in mind: If you don’t complete your maintenance requirements by the completion due date, your credential(s) will expire.
The due date for Winter '19 was April 19, 2019.
The full Expiration Policy, here, explains that
If your certification is at risk of expiring, you will ...
Taking the summary out of comments for everyone's benefit: the screens you reference are for implementation of a scenario where an external service/app is acting as a SAML identity provider, SF is a service provider.
SamlSsoConfig is the metadata object that corresponds to the Single Sign-On Settings screen, it captures a configuration of the (external) ...
The most complete list of trusted certificates that I'm aware of is here. It appears that at least some Digicert certificates are supported. Were your certificates any of the following?
You need to concatinate two certificates - your signed one and intermediate one. This literatally means opening notepad, copy and paste one cert after another, so you end up with this:
You need dowload the csr from Saleforce (Your name => configuration => secure settings => certificates => create new certificate CA) and send the csr to your CA to sign it. After that you can upload the new certificate.
Remember that the new certificate need to signed using SHA-256, And you need configurate your service to SHA-256 and TLS
This is documented at http://releasenotes.docs.salesforce.com/en-us/summer14/release-notes/communities_custom_domain_URL.htm
From that url:
From Setup, click Domain Management | Domains.
Click Add a Domain.
Enter the Domain Name.
Add a certificate if you have already set up a CA-signed certificate that supports this domain.