Configuring your App for Anonymous Access
Performing these settings will allow the App to be accessed without having an SAP Credential.
Step-by-step guide
- One-time configuration - Assigning a service user in the following services:
/sap/bc/bsp/iqx/fab_srv
/sap/iqx/fab2_srv
/sap/iqx/fab_srv
/sap/iqx/services_srv
Use tcode SICF and provide the Service Path listed above. Click on
Double click on the node
Click on and provide the service user in the Logon Data tab - For each app that needs anonymous access, ensure that the Anonymous Access flag is selected. This will create the App's url having fab_srv instead of the usual fab_bsp.
http://iqxsapdemo.cloudapp.net:8000/sap/bc/bsp/iqx/fab_srv/index.html?sap-ui-appcache=false&showlogoff=true#StartForm/FAB_DEMO_ANONYMOUS/_newForm - Passing a value in the URL parameter "email=X@X.COM" will result in having the "SubmittedByEmail" system field be set to this email. In this way the email address can be bound to the form automatically.
Note
- All back-end interaction will be carried out under the system user's user-id.
- If services exist on remote back-end ECC System (eg when developing on Gateway with /IQX/SERVICES_SRV configured via Alias to run on back-end ECC system),
- the relevant ICF node(s) on the remote system must be configured with the system user
- the system user on the remote system must have a Profile that includes Trusted RFC Access like S_RFCACL_ALL
- Locking of Tasks in the Enhanced Workflow is not available with Anonymous Access.
Related articles