Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1003
  • Last Modified:

ADFS 2.0 with Salesforce Setup

Hi Experts,

I'm trying to install and configure ADFS 2.0 to work with our Salesforce devbox.  I've followed the steps here:   http://wiki.developerforce.com/page/Single_Sign-On_with_Force.com_and_Microsoft_Active_Directory_Federation_Services

Broadly speaking I have done the following:

1.

Setup a Server 2008 Ent server, installs IIS and created a self signed cert:  hostname.<org>.local

2.

Installed ADFS 2.0 and run through the initial config wizard.  Chose the self signed certificate and set up a stand alone server farm.  No errors or warnings were displayed during configuration.

3.

Set up the correct details in the Saleforce SSO config and downloaded the metadata file.

4.

Set up a relying party trust on the ADFS server as directed and set my UPN against my Salesforce user account.
At this point I'm trying to use the SAML validator and I get the following:

 samlValidator.JPG
If I try to go to my server and log in through there I get the following:

samlLogin.JPG
I seem to be most of the way but not sure if there is a permission setting that needs changing in ADFS/IIS (which I would assume should me managed) or I've missed something out.

Any Ideas?

UPDATE:
If I log on with my local AD credentials I get the following:

certError.JPG
0
ImaCircularSaw
Asked:
ImaCircularSaw
  • 2
1 Solution
 
TheBinaryManCommented:
Hi,
 Here are a few suggestions for settings inside of your Salesforce/Force.com instance to help you with the Salesforce side of things.

Sign in normally (via the web page) to your Salesforce/Force.com instance.  By the way you will need to be an Administrator for your Salesforce/Force.com instance.

In Salesforce/Force.com go to:
1.) Username>Setup   -So you can see the Administration Setup on the lower left hand side.
2.) Security Controls>Single Sign On Settings>Edit>(Check the box & Save)
3.) Security Controls>Network Access>New>Insert your public facing IP address.(from step a. below and definetely add your IP address for the server that needs to exchange info with Salesforce)  This will stop the Salesforce instance from requiring the extra token.

To get your current ip address.  Go to:
a.)Adminsitration Setup>Manage Users>Login History>write down or copy your Source IP

Just a few extra ideas that may help you with authenticating.
0
 
ImaCircularSawAuthor Commented:
Solution was to contact Salesforce and get the organisation enabled for SSO.
0
 
ImaCircularSawAuthor Commented:
Worth while suggestions but not the solution.
0

Featured Post

2017 Webroot Threat Report

MSPs: Get the facts you need to protect your clients.
The 2017 Webroot Threat Report provides a uniquely insightful global view into the analysis and discoveries made by the Webroot® Threat Intelligence Platform to provide insights on key trends and risks as seen by our users.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now