function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
ksrksr 

Can we do the workflow process after logging in Single Sign-on?

Dear All,

 

If the user’s profile has the "Single sign-On Enabled" permission in organization level, Can that user work on the workflow process?

 

If yes, How the user name and approver name will be mapped with salesforce user object?

 

Thanks in advance.

 

--KSR 

CaffeineCaffeine

KSR,

Even in a single-sign-on environment, the sign-in name must be the same as the user's salesforce.com username (unless we are talking about a Federated case).  But in any case, SSO has nothing to do with what the user does once they are in salesforce.com.  Once they are in, they are known by their salesforce.com username.

 

Hope this helps.
ksrksr

Hello Caffeine,

 

Thanks for your reply.

 

SSO allows to validate the user names and passwords against corporate user database. If end user has logged-in with their corporate user id, how the user name and approver name could be mapped in wokflow process?

 

We would like a develop an SAAS app on the Force.complatform.

 

The application that we build on the force.com can be usedin the following ways

 

1) The application may be directly used by a corporateemployee (in this case the login credentials at their organization shouldenable them to login to the application).

 

If I understand you correctly, though the SSO enables themto login to the application they should be mapped to a salesforce.com useraccount? Is this correct?

 

2) The application may be accessed by a service provideruser who will act on behalf of a corporate. In this case the user will be ableto transact in the app on behalf of several corporate employees.

 

The challenge here is the workflow would involve theemployee's manager for approve/reject. The service provider user will not dothe approval/rejection.

 

In this case is it sufficient if we have salesforce ids onlyfor the approvers and the creator/author can be a delegated service provideruser. It will not require the corporate employees to have salesforce userid.

 

What will be the implications on the license part? Pleaseclarify. Please let me know if any of the above points are not clear.

 

Many Thanks 

 

 

--KSR

 

Message Edited by ksr on 10-29-2009 02:33 AM
CaffeineCaffeine

KSR,

In salesforce SSO, the name that the user logs in with has to be the same as the salesforce.com username. (It can be any username as longs as it is in the form of an email address).  So if you want users to login with a corporate userid, then you'll need to make their salesforce.com username that id + some email address extension (userid@company.com)

 

Salesforce.com does support Federation.   So if you have a Federated SSO system in place (one that keeps track of all the logins that a user has on different systems and issues one 'master' Federation id for the user), then the Federation Id would be used to log them in, but their salesforce.com username is still the one that they are known by in salesforce.com.