SAP S/4HANA Administration · Authentication, SSO & Communication Security

Your X.509 cert encrypts traffic whether it's self-signed or CA-signed, so why does production HTTPS still demand the CA-signed one?

Answer locked. Get the free KnowCard app to reveal it — plus spaced-repetition review so it actually sticks.

This is one card from the KnowCard library — thousands more across SAP, Linux, Python and more. In the app you get the answer, AI explanations, and cards that come back right before you would forget them. Free to start on iOS, Android or the web.

More in Authentication, SSO & Communication Security

An older integration design reaches for SAP logon tickets for cross-system SSO. Why is that the wrong call today, and what replaces them?

You're configuring SAP GUI SSO with Kerberos and jump straight to the Kerberos setup. Why does it fail, and what had to come first?

On the SAP Web Dispatcher, which PSE holds the cert for incoming HTTPS and which is for the hop out to the backend — and what symptom do you get if you swap them?

Kerberos SSO to your SAP system worked for weeks, then every user's SSO fails at once. What AD-side requirement was almost certainly violated?

Before you put a freshly configured SAP Web Dispatcher into the request path, how do you confirm it'll actually reach the backend instead of finding out from failing user traffic?

If a connection is encrypted, is the data also guaranteed to be unaltered and to come from who it claims? Why or why not?

Start learning today

Free to start — download the app or use it in your browser.