Implementing Salesforce SSO with Shibboleth

[Lior Chaga]

I understand what you mean, but at this stage I'm not concerned about different clients using our REST API.
The REST API is just the way we based our client-server architecture and the client side is developed in house. Moreover, the REST API should in fact return data for anonymous users, so it doesn't prohibit from other clients in the future to access this API, they just won't be exposed to all the data. 
Moreover, using OpenSSL, as I understand, will allow us to integrate different authentication service providers besides salesforce with little effort. So as long as our potential customers can live with federated authentication using SAML, I believe that will do the work.

Lior.



-----Original Message-----
From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: Monday, March 11, 2013 5:18 PM
To: Shib Users
Subject: Re: Implementing Salesforce SSO with Shibboleth

On 3/11/13 11:07 AM, "Lior Chaga" <Lior.Chaga at modelity.com> wrote:

>I've been following the leads and I think that what I actually need to 
>do is to have OpenSSO (or other implementation such as OpenAM) as my 
>IdP, which will perform SSO against Salesforce.
>My spring application will use OpenSSO as its authentication provider.
>
>I hope I'm on the right track...

I don't think that's likely to help you achieve non-browser access, no.

A lot of this depends on your clients, not just Salesforce. Just as knowing your IdP capabilities matters, so does what your clients will or won't support.

-- Scott


--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net