MDK Multi-User Mode Configuration
The concept name is not defined in the provided sources, and no supporting details are available to construct a grounded definition. Without a valid concept and sufficient source material, a documentation entry cannot be produced.
Tutorials that teach this
Prerequisites
- Concept Offline OData Fundamentals and Architecture The concept provided is **undefined** and no valid concept name was supplied. Additionally, the provided source snippets consist only of tutorial titles without any substantive content to ground a definition. A meaningful reference definition cannot be written without a named concept and supporting source material. Please provide a valid concept name and relevant source snippets.
- Concept MDK Project Setup in SAP Build The concept name provided is "undefined," so no specific SAP developer concept can be accurately defined. Based on the available sources, these tutorials collectively relate to the **Mobile Development Kit (MDK)**, a framework that allows developers to build and deploy mobile applications for both online and offline scenarios on SAP BTP. Developers use MDK to create cross-platform mobile apps with features such as [push notifications](https://developers.sap.com/tutorials/enable-push-notifications-mdk-public-store-client.html), deep linking, internationalization, OData-driven CRUD functionality, and NativeScript plugin integration.
- Concept MDK Project Deployment to Mobile Services The provided sources do not contain sufficient information to write a grounded definition for an **undefined** concept. The sources reference various MDK (Mobile Development Kit) tutorials and SAPUI5 deployment topics, but no specific concept is identified or described in enough detail to produce an accurate, source-grounded definition. Please provide a valid concept name and relevant source snippets.
- Concept SAP Mobile Services Account Setup and Configuration No concept was provided, and the supplied sources do not converge on a single, identifiable SAP developer concept that can be defined. A meaningful definition cannot be written without a specified concept to define.
- Concept SAML Identity Provider Trust Configuration The provided sources do not contain enough grounded information to define a concept labeled "undefined." Based on the available sources, they collectively describe **SAML trust configuration** on SAP BTP — a mechanism that allows developers to establish federated trust between SAP BTP subaccounts and identity providers (such as [SAP Cloud Identity Services](https://help.sap.com/docs/btp/sap-business-technology-platform/7c6aa87459764b179aeccadccd4f91f3?locale=en-US&state=PRODUCTION&version=Cloud) or SAP SuccessFactors) using the SAML 2.0 protocol. Developers use it to enable single sign-on, map identity provider groups to platform roles, and configure OAuth 2.0 SAML Bearer Assertion grants for secure service-to-service communication. It can also be [restored after replacement](https://help.sap.com/docs/btp/sap-business-technology-platform/21d86cf36ce94da7b2f2db8271e0b539?locale=en-US&state=PRODUCTION&version=Cloud) to recover a previous trust setup in a subaccount.
- Concept MDK Offline OData Store The concept name provided is undefined, and the supplied sources all describe tutorials related to the **Mobile Development Kit (MDK)** — a framework that allows developers to build and deploy mobile applications for SAP platforms. Based solely on the available sources, MDK supports capabilities such as [creating and modifying customer records](https://developers.sap.com/tutorials/mdk-create-customer.html), handling error archives, linking entities, and starting applications in an editor. Without a specific concept name to define, no accurate, source-grounded definition can be produced.