I’m running late this month, but this is because we are preparing great new things for mobile at the moment. Some we small appetizers we released with 1605
- Cross-origin resource sharing
- Username propagation to back-end systems
- Reports based on client usage data
- Sharing of SCIM destinations
Cross-origin Resource Sharing
This new feature let you set CORS headers via configuration. Available settings are:
Read more about CORS here: http://www.w3.org/TR/cors
Username propagation to back-end systems
This particular feature is one of my favorites this release. It’s a pretty simple thing, once select “Propagate User Name” it means that to each back-end request there will be a “X-SMP-ENDUSERNAME” header added, which contains the username, which was retrieved by the selected authentication channel (e.g. SAML).
And what is it good for? Well, your back-end system can now add this user information to apply additional filters on the data to retrieve. The client can’t manipulate this header and impersonate another user with a valid authorization.
For instance, I could send the following request:
even though my own user is “XYZ”. The back-end know can make sure that a use XYZ is not allowed to call resources belonging to ABC.
And you would use this features whenever, for any reason, you do not propagate the actual user context to the back-end and use a technical user.
Reports Based on Client Usage Data
With our SDK you can measure the usage of your app, until now we just provided you the information as raw data for further processing with SAP Lumira, or other tools.
With this release we also provide five different pre-defined reports:
Once you upload your usage data to the service, you can just navigate to “Reporting” and select “Client Log Data”, then select the timeframe and report you want to see.
And here is an example:
Sharing of SCIM destinations
Well, that’s simple. Rather than specifying a new Connection for each app-specific SCIM destination, you simply select one of the associated Connections you already have.
The workflow is simple. Just click “Override Global HCPms SCIM Configuration”, then select one of the connections you want to reuse for SCIM.
Typically, you would just re-use your OData Service Document already defined at the top of the screen – unless you have a helpful ping-service – so, click on “Save” first, then the list is populated.
That’s it for now.