Podcast #128: We chat with Kent C Dodds about why he loves React and discuss what life was like in the dark days before Git. Listen now.
3

The automatic login depends on your ADFS settings, as well as your browser's settings. First, on the ADFS server, you need to enable Windows Login (Also known as "Integrated Windows Authentication" or "IWA" for short) as an option. Note that this mode may not be compatible with Salesforce1 on Apple devices (I haven't tested this in the past two years or so, ...


3

Users cannot be deleted from a Salesforce org, the user would be deactivated.


2

You are able to make a webservice call to an LDAP service in a trigger however it will have to be via an asynchronous call to the service (so through a method defined as @future) which can then make the update as needed. If the LDAP service provides a WSDL for connecting then you can generate the needed classes in Salesforce, or use a service like this to ...


2

Salesforce1 does not support NTLM authentication. To use SSO with Salesforce1, you must use Forms Authentication. If your AD FS server is Internet-facing (not recommended), you can set external connections to Forms Authentication and internal connections to Windows Authentication, which will allow Salesforce1 to SSO correctly if you're not using a VPN. ...


2

The actual login process is as follows: User goes to a My Domain (something.my.salesforce.com). My Domain sends the user to Identity Connect via SAML. Identity Connect verifies the user's identity against Active Directory. Identity Connect sends the user to the Salesforce login with a SAML assertion. Salesforce validates the SAML assertion and gives the ...


2

Afaik there really isn't a "server directory", considering that salesforce is a distributed cloud service with a large number of shared server nodes. Since these are shared servers, there's no chance that any customer would be able to modify files on them. Frankly, I wouldn't want anyone to be able to arbitrability upload files onto those shared servers, ...


1

Directly, I do not think it is possible, however, you could create a rest API within your network to create the users and whatever else you need and then upon the appropriate event happening in SF call that API and have the user created... Some sample code to use to create a user using .net public string CreateUserAccount(string ldapPath, string userName, ...


1

This would have to be sent in the SAML response and read in ApEx. Since SF (acting as a SAML SP) is reading the attributes in the SAML response and transforming them to a Map which is then passed to your ApEx code, the answer to your question largely depends on how your identity provider transmits these groups. As a lowest common denominator, if each group ...


1

Single Sign-On with Force.com and Microsoft Active Directory Federation Services gives this advice: When configuring ADFSv2 for use with Salesforce, it's recommended that you select the new "HTTP Redirect" option available in the Salesforce Single Sign-On settings under "Service Provider Initiated Request Binding". This will improve interoperability ...


1

You cannot directly interface with an LDAP data source from apex. The only supported way of calling a remote service via apex is either HTTP(S) or SMTP (aka email; not helpful here). As @pbattisson mentioned there are some middleware applications that allow proxying LDAP to and from HTTP(S) data. Be it a RESTful or SOAP-based stack apex should support them ...


1

According to Single Sign-On for Desktop and Mobile Applications using SAML and OAUTH, you can get your application to send the user to just the accept/deny page directly by using a web browser internal to your application. This is how the Chatter Desktop application and other Salesforce offerings work.


Only top voted, non community-wiki answers of a minimum length are eligible