Kitsilano Technologies

SSL for SAP

SSL certificates for your SAP systems.

Certificates for Fiori, the SAP Web Dispatcher, NetWeaver and S/4HANA, chosen for your landscape and installed inside SAP by the team that runs SAP on AWS for businesses worldwide.

Organisation validatedInstalled through STRUSTRenewals tracked

Where it goes

An SAP system has more than one place to put a certificate.

Which one matters depends on where users and partners connect. Getting that right decides how many names the certificate needs, and therefore which one to buy.

SAP Web Dispatcher

The usual front door for Fiori and anything reached from outside. It holds the certificate users see, in its SSL server PSE, so this is where most SAP certificates go.

NetWeaver AS ABAP and S/4HANA

Each application server presents its own certificate over HTTPS, managed in transaction STRUST. Needed when users or interfaces reach the server directly rather than through the Web Dispatcher.

NetWeaver AS Java and Enterprise Portal

Certificates live in the Key Storage of NetWeaver Administrator. Portals and PI or PO systems that partners connect to need one on a public name.

SAP BTP custom domains

Your own domain on BTP applications, such as apps.company.com, needs a certificate uploaded through the Custom Domain Manager, which also generates the request.

SAP cloud services such as SuccessFactors, Ariba and Concur run on SAP's own certificates, so they need nothing from you.

Certificates for SAP

Choose by how many SAP addresses you have.

All three are organisation validated, so the certificate carries your verified company name, which is what auditors and banks expect on a business system.

One SAP address

fiori.company.com

Sectigo

InstantSSL

A single Fiori launchpad or Web Dispatcher address. The lowest cost way to put your verified company name on it.

$95

per certificate, per year

Covers
One domain, plus its www form
Issued in
1 to 3 business days
Read more

A landscape: production, quality and development

sap.company.com, sapqas.company.com, sapdev.company.com

Sectigo

Sectigo Multi-Domain OV

Four names included, with room to add more, so one certificate covers the systems in your landscape and renews once.

$240

per certificate, per year

Covers
Four domains, extendable to 995
Issued in
1 to 3 business days
Read more

Many SAP hosts under one domain

*.sap.company.com

Sectigo

InstantSSL Premium Wildcard

Every host under one name, including systems you add later. Simplest to run, but the same key sits on every system that uses it, so we usually keep production on its own certificate.

$405

per certificate, per year

Covers
Unlimited subdomains of one domain
Issued in
1 to 3 business days
Read more

Check your names before you buy

Public certificates only cover public names. A host like sapprd.corp.local or a bare IP address cannot be issued one by any certificate authority, so it needs a public name (usually through the Web Dispatcher) or a certificate from your own internal CA.

Installed inside SAP

On SAP, the certificate is the easy part.

SAP does not take a certificate file the way a web server does. The request is generated inside SAP and the signed certificate is imported back into its own store, so our SAP engineers do the whole job.

  1. 01

    We confirm the names

    Which hostnames users and partners actually reach, and that each is a public name. This is where most SAP certificate orders go wrong, so we check it before you pay.

  2. 02

    The request is generated inside SAP

    The private key is created in STRUST, sapgenpse or the Web Dispatcher and never leaves the system. We send the request it produces to the certificate authority.

  3. 03

    Your company is validated

    One to three business days for organisation validation: your company registration, tax registration and a call to a listed company number.

  4. 04

    We import and activate it

    The signed certificate goes back into the PSE with its full intermediate chain, the ICM or Web Dispatcher picks it up, and we test Fiori, SAP GUI for HTML and your interfaces before handing over.

Renewals

Certificates now expire within months, not years.

The certificate authorities and browsers have agreed to shorten certificate lifetimes in stages. On most web servers renewal can be automated. On SAP each new certificate is reimported into the PSE, which is easy to forget until Fiori stops loading.

  • We track the expiry of every certificate we supply
  • We reissue and reimport it into SAP before it lapses
  • Reissues within the term you bought carry no extra licence cost
Since March 2026
200 days
From March 2027
100 days
From March 2029
47 days

Running SAP on AWS?

Where Fiori is published through an AWS load balancer, AWS issues and renews that certificate at no cost, and you only need one where SAP itself handles TLS. We will tell you which applies to your landscape before you buy anything.

SAP on AWS with Kitsilano

Questions

SAP certificates, answered.

Which certificate does SAP Fiori need?

Fiori needs a certificate on the address users open, which is usually the SAP Web Dispatcher. An organisation validated certificate is the normal choice for business systems. Use a single name certificate for one address, a multi-domain certificate to cover production, quality and development together, or a wildcard for many hosts under one domain.

Can I get a certificate for sapprd.corp.local or an internal IP address?

No. Since 2015 no public certificate authority may issue certificates for internal names or private IP addresses. Either publish the system under a public name, usually through the Web Dispatcher, or use a certificate from your own internal certificate authority. We can help with either.

Can we generate the CSR ourselves?

Yes. Create it in STRUST for the SSL server PSE, with sapgenpse for the Web Dispatcher, or in the Custom Domain Manager on BTP, then paste it at checkout or send it to the certificate desk. Generating it inside SAP keeps the private key on the system that uses it.

How often will we need to renew?

More often than before. Industry rules cut the longest a certificate can last to 200 days in March 2026, 100 days in March 2027 and 47 days in 2029. A multi-year purchase stays one subscription, but the certificate itself is reissued and reimported into SAP several times a year. We track the dates and can do each reimport for you.

Our SAP runs on AWS. Do we need to buy a certificate?

Not always. Where Fiori is published through an AWS load balancer or CloudFront, AWS Certificate Manager issues and renews the certificate on the load balancer at no cost, and we set that up as part of SAP on AWS. A purchased certificate is still needed wherever SAP itself terminates TLS, such as the Web Dispatcher or the application servers.

SAP certificate desk

Tell us about your landscape.

Send us the SAP addresses your users and partners reach, and we will tell you which certificate covers them and how we will install it.