Configuration Properties
Properties that you can use to configure SAP Fiori Client.
The following minimum properties are required to configure SAP Fiori Client:
- appID
- fioriURL
- fioriURLIsSMP
Property |
Description |
---|---|
appID |
Identifies the application to the datavault. If you use SAP Mobile Platform Server or SAP HCP, mobile service for development and operations, this must match the app ID of the target application. For more information, see Defining SAP Fiori Client in SAP Mobile Platform. |
fioriURL |
Full URL of the target application.
|
fioriURLIsSMP |
Set this to true if SAP Fiori Client connects through SAP Mobile Platform Server or SAP HCP, mobile service for development and operations. |
certificate |
Client certificate provider. If you use SAP Afaria, specify com.sap.afaria as the certificate provider. For examples, see X.509 Configuration Examples. |
federated_certificate |
Configure certificate federation. Set the certificate property to com.sap.federationprovider, and set the federated_certificate property to your certificate provider. For example: “certificate”:”com.sap.federationprovider”, “federated_certificate”:”com.sap.afaria” For more examples, see X.509 Configuration Examples. For more information about certificate federation, see FederationProvider Plugin. |
autoSelectSingleCert |
(iOS only) Whether the application automatically selects a client certificate for mutual authentication. The default value is false. |
appName |
Customize the application name shown on the logon screen and on the device. The default app name is SAP Fiori Client, defined in the resource file. |
passcodePolicy |
Specifies the passcode policy of the datavault. If you use SAP Mobile Platform Server or SAP HCP, mobile service for development and operations, the passcode policy is determined by the server. The default passcode policy is: "passcodePolicy":{ "expirationDays":"0", "hasDigits":"false", "hasLowerCaseLetters":"false", "hasSpecialLetters":"false", "hasUpperCaseLetters":"false", "defaultAllowed":"true", "lockTimeout":"300", "minLength":"8", "minUniqueChars":"0", "retryLimit":"10", "allowFingerprint":"true" }, For more information, see Application Passcode |
keysize |
Optional argument for the SAP Afaria certificate provider that sets the bit rate of the public/private keys. The default value is 2048. |
idpLogonURL |
Reloads the identity provider (IdP) logon with the user name and passcode passed from the SAP Authenticator app for single sign-on (SSO). For more information, see Configuring Single Sign-On with One-Time Password (OTP) and SAP SSO. |
nobridgewhitelist |
Specify additional domains that can access plugins provided by SAP Fiori Client when loaded into the app's WebView. For example: "noBridgewhitelist":["yahoo.com","google.com"] To disable the No Bridge security feature, use the wildcard character: "noBridgewhitelist":["*"] For information about the No Bridge security feature, see No Bridge for Non-Fiori Content. |
multiUser |
Enable multiple user support on the Custom SAP Fiori Client. Multi-user mode allows multiple users to register and use the same SAP Fiori Client application. Use "multiUser":true to enable multiple user support. Use "multiUser":false to disable multiple user support. For information about multiple user support, see Enabling Multiple User Support. |
proxyID |
Specify the preference name in config.xml for creating a proxy library instance based on the platform class name. This property is supported only on the iOS platform. For information about proxy support, see Supporting Pulse Secure. |
proxyURL |
Specify the proxy library URL setting. This property is supported only on the iOS platform. For information about proxy support, see Supporting Pulse Secure. |
proxyExceptionList |
Specify the proxy exception list using regular expressions. Any requests with a matched URL should be handled by the secure proxy library, and ignored by the application connection handler. The list should include proxy URLs and SAML IdP URLs. This property is supported only on the iOS platform. For information about proxy support, see Supporting Pulse Secure. |