Symptom
You have noticed a new user-agent in the OData API audit log and want to find out more about it.
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
Environment
SAP SuccessFactors Mobile
Cause
Product Enhancement
Resolution
FAQ:
Q1) Was this change caused by a new update?
A1) Yes. Our internal reference for this change is MOB-81493. The reason for the change is that the different SAP SuccessFactors modules needed to identify whether a call is coming from a Mobile device or the Web.
Since Android and iOS already send a user-agent header, we wanted to capture this information for API activities also (within the BizX infrastructure).
Q2) In the past, the user agent "SF_MP" represented access from the mobile app. Currently, we are still seeing the "SF_MP" user-agent in our logs. Will the "SF_MP" user-agent be completely replaced with the new JSON information?
A2) Currently, the new User-Agent only applies to APIs which support both Web and Mobile; for the old APIs the SF_MP headers are still there. The plan long term is to remove SF_MP as new APIs roll out the new header gradually, however there currently is no ETA on the removal of SF_MP and no schedule available as to what APIs will roll out the new headers.
Q3) Does this new JSON format only apply to users with a newer app version? or will it apply to all users and versions?
A3) No, it applies to all the APIs regardless of client version as it’s a server change.
Q4) Is this change impacting selected API entities only (e.g. "Photo" or "EmployeeProfilePageConfig"?
A4) No. Individual functions are not being impacted, only the technical information (please bear in mind that the header SF_MP is used for traffic checking only).
Keywords
MOB-81493, user-agent, header, headers, OData API, OData, API, Mobile, Audit Logs, Audit Log, JSON , KBA , LOD-SF-INT-ODATA , OData API Framework , LOD-SF-INT , Integrations , LOD-SF-PLT-MOB , Mobile Issues , Product Enhancement