Add ConnectHealthMD White Label Template

[connecthealthmd]

Description

Adding a new template for the ConnectHealthMD white-label service. This allows professionals to connect their subdomains (e.g. www) to our SaaS edge.

Type of change

• New template
• Bug fix (non-breaking change which fixes an issue in the template)
• New feature (non-breaking change which adds functionality to the template)
• Breaking change (fix or feature that would cause existing template behavior to be not backward compatible)

How Has This Been Tested?

• Schema validated using JSON Schema template.schema
• Template functionality checked using Online Editor
• Template is checked using template linter
• Template file name follows the pattern <providerId>.<serviceId>.json
• resource URL provided with logoUrl is actually served by a webserver

Checklist of common problems

• digital signatures are used and syncPubKeyDomain specified
  • Comment: Public template, syncBlock is false.
• syncRedirectDomain is specified when intended to use redirect_uri parameter in the synchronous flow
• no TXT record with SPF content (i.e. "v=spf1 ...") instead of using SPFM record type on APEX
• txtConflictMatchingMode is set on TXT records which shall be unique on a label (like DMARC)
• variables are set to the smallest scope needed
• no variables as a host name to apply template on subdomain instead of standard host parameter
• no explicit usage of %host% variable in host attribute
• essential setting is used on records, which the user shall be able to change or remove manually later without dropping the whole template

Example variable values

verifyToken: a1b2c3d4e5f6

[github-actions]

Linter OK:

Linter result for connecthealthmd.com.white-label.json

[kerolasa]

Looks good to me.

[pawel-kow]

@connecthealthmd you wrote

• digital signatures are used and syncPubKeyDomain specified
  Comment: Public template, syncBlock is false.

How are these 2 things related? Is your intention, that the apply link would be created by multiple parties so that signing is impossible?

[connecthealthmd]

@connecthealthmd you wrote

• digital signatures are used and syncPubKeyDomain specified
  Comment: Public template, syncBlock is false.

How are these 2 things related? Is your intention, that the apply link would be created by multiple parties so that signing is impossible?

@connecthealthmd you wrote

• digital signatures are used and syncPubKeyDomain specified
  Comment: Public template, syncBlock is false.

How are these 2 things related? Is your intention, that the apply link would be created by multiple parties so that signing is impossible?

Thanks for pointing that out. I have updated the template to support standard RSA signatures (syncPubKeyDomain and syncPubKey added). Our setup is now live.

[pawel-kow]

@connecthealthmd I recommend reading the specification and not trusting that your AI tool will do the work properly! They are pretty good at hallucinating properties not existing in the specification.

[connecthealthmd]

@connecthealthmd I recommend reading the specification and not trusting that your AI tool will do the work properly! They are pretty good at hallucinating properties not existing in the specification.

I should've trusted my instinct instead of having it reviewed before I submitted and convincing me otherwise.

@connecthealthmd I recommend reading the specification and not trusting that your AI tool will do the work properly! They are pretty good at hallucinating properties not existing in the specification.

Yup, my apologies for putting in the wrong property. I re-read the spec and syncPubKey does NOT exist. I removed it from the JSON and left the syncPubKeyDomain exactly as the spec described. If anything else is needed I will make the changes myself without considering other opinions.

[pawel-kow]

Thx