Special Authority Transformation

Developer setup

This requires SFDX CLI installed and authenticated with a DevHub org with the alias, devhub.

$ ./dev-setup.bat

Common Salesforce CLI Commands

Delete scratch org.

$ sfdx force:org:delete -u sat-dev

List changes between project and scratch org.

$ ../MoH-SAT> sfdx force:source:status

Pull changes from scratch org into project.

$ ../MoH-SAT> sfdx force:source:pull

Push changes in project to scratch org.

$ ../MoH-SAT> sfdx force:source:push

Miscellaneous Commands

Reset local main branch. This wipes out any local changes in main.

$ ../MoH-SAT> git fetch --all
$ ../MoH-SAT> git checkout main
$ ../MoH-SAT> git reset --hard origin/main

Create a new feature branch from main.

$ ../MoH-SAT> git checkout main
$ ../MoH-SAT> git pull
$ ../MoH-SAT> git checkout -b <name_of_branch>

Package Upgrade

sfdx force:package:version:create -v devhub -d force-app -f config/project-scratch-def.json -x -p "Special Authority App" -w 15 -c

Package Installation

Run any manual pre-install steps.

Deploy package dependencies in source control.

$ ../MoH-SAT> sfdx force:source:deploy -p dev-app-pre -u <sandbox>

Install package version.

$ ../MoH-SAT> sfdx force:package:install -p 04t... -u <sandbox> -b 15 -w 15

Deploy post-install package configuration in source control.

$ ../MoH-SAT> sfdx force:source:deploy -p dev-app-post -u <sandbox>

Run any manual post-install steps.

Inbound REST API Documentation

See here for API specification and documentation

Certificates setup for ODR Connection

General configuration steps:

Setup a Named Credential
Create a self-signed cert
Secure access to PFX file from ODR
PFX to JKS conversion
Import JKS
Configure Named Credential Certificate
Enable Identity Provider
Testing

Setup a Named Credential:

Best practise in salesforce is to make authenticated calls from within Apex to external services using a named credential. This simplifies the connection handshake and allows your Apex code to be cleaner and portable to other orgs/environments.

Follow detailed instructions here

Create a self-signed cert:

From Setup, search for Certificate and Key Management in the Quick Find box.
Select Create Self-Signed Certificate.
Enter a descriptive label for the Salesforce certificate.
Enter a unique name.
Select a key size for your generated certificate and keys.
Click Save

Now your Salesforce org is able to Import a JKS file (it won't be able until this step)

More detailed instructions here

Secure access to PFX file from ODR:

Make sure you receive the PFX certificate file and it's password securely from the ODR custodian.

PFX to JKS conversion:

Salesforce does not support PFX, but JKS (Java Key Store). You must first convert it to JKS before importing it in setup.

Make sure you have keytool command line utility from Java installed. OSX will have this natively installed in the terminal.

In order to convert the PFX file correctly, you need to obtain the source alias used for the certiicate. To obtain that, run the following command:

keytool -list -keystore <your file name here>.pfx -storetype pkcs12

The output will be similar to the following:

Keystore type: PKCS12
Keystore provider: SUN

Your keystore contains 1 entry

MyCertificateAlias, Nov. 3, 2020, PrivateKeyEntry, 
Certificate fingerprint (SHA-256): CF:80:A2:59:16:FC:FE:8A:D6:5A:7B:AF:80:A8:22:09:89:8A:DF:52:61:20:DB:71:26:12:36:D4:14:88:9D:C1

In the case above, the alias is MyCertificateAlias.

You can now use that alias and generate the JKS file. It will ask you for the passphrase to use for encrypting the key and the passphrase of the pfx file. Use the same password for encrypting as decrypting.

keytool -importkeystore -srckeystore <your cert file name here>.pfx -destkeystore keystorefile.jks -srcstoretype pkcs12 -deststoretype jks -destalias <name_your_certificate_here> -srcalias MyCertificateAlias

This will generate a file called keystorefile.jks.

Import JKS:

You can now load the keystorefile.jks file created above into Certificate and Key Management in Salesforce Setup. Click the Import from Keystore button and select the jks file and put in the password you used in the above step.

Add Cert to Named Credential:

Make sure to go back to the named credential you configured in the first step, and select the cert you just created.

Enable Identity Provider

In Salesforce, go to Setup -> Identity -> Identity Provider -> Enable. Select the certificate you named when importing the JKS.

Testing

At this point, your SSL cert and named credential should be linked up, and you will be able to call your named credential in Apex code easily. See below for an example:

HttpRequest req = new HttpRequest();
req.setEndpoint('callout:My_ORD_Named_Credential/path/to/endpoint');
req.setMethod('GET');
Http http = new Http();
HTTPResponse res = http.send(req);
System.debug(res.getBody());

References

Salesforce Development with Visual Studio Code

Lightning Web Components Library and Documentation

marklise / MoH-SAT