cancel
Showing results for 
Search instead for 
Did you mean: 

IPS Requirement to Activate People Analytics

Marco_Re
Explorer
0 Kudos

Dear community,

we are currently starting rotating toward SAP SuccessFactors People Analytics . The activation process requires SAP Identity Management  (IPS) to be configured: in our environments IAS is used as a Proxy towards an external Identity Provider (Azure).
Hence IAS/IPS is not used as an active User/authorization Management system.
in this context, will IPS adoption still be mandatory, and if yes, should we actively switch from a proxy IAS implementation to an active User management on IAS/IPS?

is there any additional technical documentation to be checked?

thanks everyone for the help,

Accepted Solutions (1)

Accepted Solutions (1)

dyaryura
Active Participant
0 Kudos

Hello Marco

If you have already enabled IAS for SuccessFactors, the configuration for PA is simple. You do not need to change your proxy configuration in IAS. The Task in upgrade center will automatically create a new target system in IPS. You basically need to review it and enable considering that your SF instance will be the Source System.

you can check for reference: https://dam.sap.com/mac/app/p/pdf/asset/preview/qzbPnKT?ltr=a

an there are also notes like: https://me.sap.com/notes/2877303/E

Note that you might have more complex configurations in your environment, but for a simple scenario where you have already migrated to IAS, it can be solved easily.

I'd assume that proxy configuration will be always possible in general for all SAP Products since this is a supported setup suggested by SAP. In this scenario, users won't notice that IAS is in the middle. The Issue with most new SAP SaaS solutions is that they require to have a local user store (in this case in SAC). SAP Is providing IPS to solve this problem of user replication, but in terms of proxy, your user will log on to SF and should get a SSO experience without issues.

 

Marco_Re
Explorer
0 Kudos
thank you dyaryura! very interesting documentation.

Answers (0)