SAP BTP · Cloud Identity Services: Authentication & Provisioning

On an application's Trust tab in Identity Authentication Service (IAS), the authentication type is already set and differs between two subaccounts you manage. What determines whether it defaults to SAML 2.0 or OIDC?

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 Cloud Identity Services: Authentication & Provisioning

An admin hand-edits a few user attributes directly in the IPS target system, then the scheduled Read Job runs. What happens to those manual edits, and does switching to a Resync Job protect them?

You need to trust your own certificate authority for X.509 client-cert logins and route IAS notification emails through your company SMTP server. Are these per-application settings, and where do tenant-wide options like these live?

If asymmetric encryption solves symmetric's key-exchange problem, why don't modern connections just use asymmetric encryption for everything?

You want Identity Authentication itself to act as the source system in an Identity Provisioning job. What must you set up in IAS first so IPS can even read from it?

Besides username/password, what authentication methods can SAP BTP use?

A partner needs to administer your BTP global account using an X.509 client certificate for automation. They currently log in with a self-registered P-user. Will that work, and what must change?

Start learning today

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