2088591 - Offline Documents: How to Make Offline Forms Work with SSO Implementations - Platform

SAP Knowledge Base Article - Public

2088591 - Offline Documents: How to Make Offline Forms Work with SSO Implementations - Platform

Symptom

  • How do I make Offline Forms work with SSO (exception: SAML SSO)?
     
  • SuccessFactors contains an offline forms feature which allows a user to download a form that is still in progress and be able to edit it while they are offline.  When they are later able to reconnect online, they can then submit these form changes to the SF server and continue on with their process as before.

    SF supports SSO with the offline forms feature for all implementations of SSO except SAML.  In order to support this, a URL is required for a backend setting that will override the submit button URL that is displayed on the offline form.  When submitted, all the form data will be stored in an http POST and sent to the server at the URL.  This server will then have the responsibility of forwarding the post data to the URL: https://performancemanager.successfactors.com/offlineform which should also contain the SSO information required to login.

Environment

  • BizX Platform

Resolution

  • SuccessFactors contains an offline forms feature which allows a user to download a form that is still in progress and be able to edit it while they are offline.  When they are later able to reconnect online, they can then submit these form changes to the SF server and continue on with their process as before.

    SF supports SSO with the offline forms feature for all implementations of SSO except SAML.

    The solution does require that the client setup the needed implementation as documented below for this feature to work.

 

Offline URL Redirect

  • This URL is required information for SuccessFactors to be able to override the normal offline form submit button, which usually forwards to SF’s own servers, to a custom URL that should point to a client server; usually at a script or servlet point of access.  This action should forward all of the form data and changes to the server via an http POST.  Do note that the Owner Password input element seen on the form will require the password for the client’s portal or intranet, not the SuccessFactors password.
     
  • Handling the Request and Forwarding.
     
  • Once the server has received the request, it will need to obtain two key pieces of information: the username and password.  If multiple company instances are being utilized in the SuccessFactors application for the particular company, a company id will be required.  They can be retrieved through the following http request parameters:

    Username => pmoff_docowner

    Password => pmoff_password

    Company => pmoff_companyid
     
  • These parameters should be used to login the user in to their intranet/portal and route them to a specific script or servlet that will render an SSO URL and forward the http POST data to it.  This URL should look similar to the URL that is generated with the regular SSO implementation but with one difference: instead of pointing to /login, it should point to /offlineform.

 

Forwarding the Post

Keywords

KBA , sf sso , LOD-SF-PLT , Foundational Capabilities & Tools , How To

Product

SAP SuccessFactors HCM Core all versions