Best Practice: Disable Direct Login to Salesforce – Transaction Security Policy

The implementation of Single Sign On (SSO) is a standard requirement for enterprises. SSO not only makes the login processes more comfortable for user, it as well allows companies to centrally control the access to applications. To enable central control it is required that SSO is the only option for users to access the application.

In Salesforce a user with SSO enabled has two options to access the system: (1) Using Single Sign On and (2) Username and Password.

To disable access to Salesforce additional features must be configured:

Disable login.salesforce.com (not enough)

The first option is to implement Salesforce My Domain, use the Identity Provider as the only option for login via My Domain and disallow users to login from login.salesforce.com.

Untitled.png
Salesforce My Domain Settings

This option can be circumvented by users. They can still use <mydomain>.my.salesforce.com/?login to access the application and enter there username and password.

Salesforce My Domain with login parameter

User Setting “Is Single Sign-On Enabled”

One way to disable login via Username and Password is the User Setting “Is Single Sign-On Enabled”. The setting comes as part of “Delegated Authentication”.

The documentation of the user feature is minimal. Salesforce is referring to it only in a handful of articles. It seems like the feature was intended to route the username and password after entering it to the “Delegated Authentication Web Service” and not to disable other login mechanisms.

If the user’s profile has the Is Single Sign-On Enabled user permission, then Salesforce does not validate the username and password. Instead, a Web services call is made to the user’s organization, asking it to validate the username and password.

Single Sign on for Desktop and Mobile

The setting can be enabled on Profile and Permission Set Level without entering the address of the delegated authentication service. This results in the side effect that users cannot login with Username and Password. Users that try to login with their username and password will see the following error message:

We can’t log you in because you’re only allowed to use single sign-on. For help, contact your Salesforce administrator

Error Message after entering username and password

This behavior has been documented by Ashish Agarawal and multiple others on StackExchange. However, the feature is not officially documented and can be removed at anytime. I would personally not recommend to go this route.

Transaction Security Policy – Salesforce Event Monitoring

Since 2016 Salesforce Orgs can be protected with Salesforce Shield. As part of Shield specific Transaction Security Policies can be enforced. Based on policies different transactions e.g. Logins or Report Exports can be prohibited. The setup of a new Transaction Policy is done in 3 steps:

Step 1: Setup Event Monitoring

Transactional Policies are based on Salesforce Event Monitoring. After the feature licenses for Shield is activated, event monitoring can be activated:

Activate Event Monitoring

Step 2: Create a new Policy

Policies are based on three components: (1) a listener, (2) Condition, (3) Reaction. In the first step of the setup the event type must be selected (in this example “Login”) and the corresponding Resource “Login History”.

For each event defined in the listener a short piece of code is executed. The “Condition” detects if the policy is violated and triggers the reaction.

Create new Login Policy

In the 2nd screen the reaction of a policy violation is configured. In this case the login is blocked and the administrator is informed via Email.

Reaction for a given Policy

Step 3: Write a Policy Condition

In order to restrict the login from any other identity provider that the one that has been selected, I implemented a short APEX class. The class checks for each login if the right Authentication Service is used.

global class LoginPolicyViolationPolicyCondition implements
TxnSecurity.PolicyCondition {
    private static final String ALLOWED_AUTHENTICATION_SERVICE_ID = 'XXXX';

    public boolean evaluate(TxnSecurity.Event e) {
        String loginHistoryId = e.data.get('LoginHistoryId');
        LoginHistory l = [   SELECT Id, AuthenticationServiceId FROM LoginHistory WHERE ID =: loginHistoryId ];
        return ALLOWED_AUTHENTICATION_SERVICE_ID !=
            String.valueOf(LoginHistory.AuthenticationServiceId);
    }
}

Finally

Salesforce Shield is the out of the box way to detect violations of policies and react accordingly. In comparison to the “Delegated Authentication option” the policies are designed to inform administrators about cases of violation.

News.Simple-Force

Keeping up with the latest news from the Salesforce Universe has not always been easy. Today more than 100 blogs exist in the Salesforce Universe. To keep up with what is new, I have built “News.Simple-Force” – a Salesforce news aggregator.

News.Simple-Force – The Salesforce News Aggregator

The website is incredible easy to use. Every hour the news aggregator checks for the latest news from the most known Salesforce Blogs. By visiting news.simple-force.com users can see what’s new in the world of Salesforce.

Right now the news aggregator only takes blogs into account. However, in the future more functions can follow such “most recent and highly noticed StackExchange Articles” or new videos posted by Salesforce and others on Youtube.

SDFDX: Salesforce Package Versions depend on Scratch Org Definition

While implementing a Salesforce Package Version for my private Salesforce package, I encountered an interesting fact: The creation of the Salesforce Package Version is only possible if the right corresponding Scratch Org Definition file is provided.

Scenario

I noticed that the issue when I wanted to create a custom field that is dependent on the “Person Account” feature.

1. I first modified my scrtach org permission file to enable personaccounts.

1.png

2. I created a new scratch org.

2.png

3. After creating and adding a new field that dependet on Person accounts, I tried to create a new package version.

5.png

4. My new package version was rejected with the following error message:

ERROR:  Account.Person_Account__c: Field IsPersonAccount does not exist. Check spelling.

6.png

The error message does not indicate what is actually the issue. The system just suggest that the IsPersonAccount field is not existing.

Solution

The solution is comparable obvious. The Scratch Org Definition File is missing. As indicated in the documentation the file is not mandatory. However, it is required in case the package is dependent on specific Salesforce Org Features:

-f | –definitionfile DEFINITIONFILE Optional

The path to a definition file similar to scratch org definition file that contains the list of features and org preferences that the metadata of the package version depends on.

Type: filepath

By including the scratch org definition file the package version could be created easily without any further issues.

7.png

Learning: The scratch org definition file is not mandatory, but required in case the package is refering to any specific Salesforce feature.

Marketing Cloud: External Editors

Salesforce Marketing Cloud is a fantastic tool for Marketing Automation. I had the chance to participate in small and large scale Marketing Cloud implementation. As a result of that I developed several best practices such as the use of external editors.

External Editors such as c9.io or codesandbox.io have been essential for me for two reasons: (1) Version Control, (2) faster round-trip time.

Setup – External Editor

In the first step an external editor must be chosen. I recommend c9.io or codesandbox.io. In both cases the editor is able to serve content via HTTP.

The Editor is used to write Server Side Javascript or AMPscript.

codesandbox.io

In the example above you can see a quick “hello world” AMPscript.

Cloud Page to Execute the Code

To execute the code in Marketing Cloud a simple Cloud Page must be created. The Cloud page is able to load content from an external server and execute the Javascript and AMPScript that is visible on the page.

%%= TreatAsContent(HTTPGET("http://www.myserver")) =%%

Now only the cloud page must be loaded and the result is visible.

Development Lifecycle

The resulting development lifecycle is easy and fast:

  1. Code is written in the editor and saved.
  2. By reloading the cloud page the result is visible.

SFDX: Let’s get started – My first unlocked namespaced package

Some time ago, Salesforce released Salesforce DX. With the Winter Release 2019 the DevHub became available for Developer Orgs. Together with the 2nd generation of packaging it is now possible to create unlocked and managed packages with Namespaces. In this article I quickly describe the steps to create a developer controlled (unlocked), namespaced package.

Step 1: Dev Hub

To enable a Salesforce DevHub, I had to sign up for a new Developer Edition. The DevHub runs only correctly if  “my domain” is enabled and NO namespace is assigned to the DevHub Org.

Step 2: Namespace Org

For the registration of a Namespace (that is globally unique) a 2nd org must be setup. In the Menu (Setup -> Packages) I registered the Namespace “simpleforce”.

Screen Shot 2018-10-27 at 18.53.43.png

Step 3: Link Namespace to DevHub

Before linking a Namespace to the DevHub, my domain must be enabled. Without my domain the “Link Namespace” button is not visible.

Screen Shot 2018-10-27 at 18.57.53.png

The Linking Process is done in 2 steps: (1) I had to enter username and password of the org that holds the namespace. After confirming that the DevHub has access to that org, the namespace is linked to the DevHub.

Step 3: Setup Project

To create a namespaced package, a new project must be setup. A project can contain multiple packages. In my case the project is called simple-force:

sfdx force:project:create --name simple-force

A single DevHub can link multiple Namespaces. But a project can be only linked to a single Namespace. The namespace must be specified in the Project Definitional fine:

Screen Shot 2018-10-27 at 19.01.14.png

From now on all packages creates in this project will be part of the selected Namespace.

Step 4: Create the Package

To separate components that belong to my new package “ulog” from other components, I created a new folder and registered a new package called “ulog”:

mkdir ulog

sfdx force:package:create --name ulog --packagetype unlocked --path ulog

Screen Shot 2018-10-27 at 19.10.58.png

The created package is empty. I created a new scratch org and deployed the universal logger in to the scratch org. Using the force:source:pull command all components of the scratch org are getting downloaded:

// create scratch org
sfdx force:org:create -f config/project-scratch-def.json -u devOrg

// pull content
sfdx force:source:pull -u devOrg

To choose which components are part of my package, I moved the relevant components from “force-app” to the “ulog” folder:

Screen Shot 2018-10-28 at 14.22.10.png

Components such as profiles that are not needed for the package are not moving to the new folder.

After all components are in the right package folder. A new version of the package had to be created.

sfdx force:package:version:create -p ulog -x -w 10

All components are getting uploaded to Salesforce. And the new package becomes available for other orgs to install.

Step 5: Install the Package

To check if the package can be installed in a new org, I created a new scratch org and installed the package:

sfdx force:org:create -f config/project-scratch-def.json -u valorg

sfdx force:package:install -p 04t1t000001yUV2AAM -u valorg -w 10

Finally the package is successfully installed and my first namespaced package created!

My 10th Year in the Salesforce Ecosystem starts today

Back on August 25th 2009 I registered by first Salesforce Account. Since that time Salesforce has been the driver of my personal and professional life. I’m very thankful for the time and the people I met.

It is time to look back:

Salesforce as a University Project

In 2008 I started studying at the University of Mannheim. In our 3rd semester one of our new professors. Professor Mädche announced that a project will be part of his course “Wirtschaftsinformatik 2” (Information Systems 2). In the project we had to use a new Cloud Computing Platform to build a simple business process: The platform was Salesforce.

To learn more about Salesforce we, a group of friends and I, visited one of the early Salesforce Events “Cloudforce Essentials in Stuttgart”. We met Andreas von Gunten. Andreas called himself a Cloud Evangelist. He was the founder of a small Salesforce Consultancy called PARX and convinced companies in a speech to use future technology: Salesforce.

I was very impressed and tweeted that I met my the first “Evangelist” in my life. During lunch Andreas came over. He saw my tweet. We started chatting and explained the purpose of our visit: Learning more for our project. He offered to help us and we stayed in touch.

Back in Mannheim, I talked to our professor and he right away invited Andreas to give a speech in one of his lectures.

With two of my friends we started the Salesforce project. Lucky me, I took a video of it:

Wifo2 from Christian Deckert on Vimeo.
After our project was over, I started my first Salesforce Job as a Hiwi (Student Assistant). My job was to implement Salesforce for the chair of the professor. I implemented automations for book orders, chatter, opportunities and more.

During that time I visited my first Salesforce Conference in Frankfurt and took a photo with Sassy:

23489_370569559354_564094354_3706469_2303366_n-1_1__400x400-1.jpg

Salesforce Consultant @PARX

At the end of the 4th semester in Mannheim, I had to find an internship. It was part of my curriculum. I reached out to Andreas. I asked if I can stay for a 3 month internship. I did my first interview and was asked to say for 6 months. My university teachers told me that the curriculum was designed to run in sequence, and that missing half a year will get me out of the rhythms of studying. I decided to extend my work at PARX by another 6 months.

My first year in Zurich. PARX was a very small company. The company was already mainly focused on Salesforce. I got a lot of freedom for a 21-year old. One of my first projects was building a Web-Shop based on Salesforce Sites (a brand new technology).

This project became my companion for the next couple of years. I’m still proud of it. Especially since I developed multiple versions of it. Including a small framework for Websites on the Salesforce Platform: Die Akademie.

After the first year, I decided to stay with PARX and continue studying on the side. Over the years at PARX, I met a lot of great people: Beat, Manuel, Thomas, Michel… all great people. As in very job we had great and not so great clients. However, the majority was amazing: starting with the local groupon clone, an energy grid provider, a fashion company and more. More of my friends needed jobs / internship. Overall 5 people started, 4 of them are still very successful in the Salesforce World.

In 2012 I finally finished and got my Bachelor’s degree.

I worked for a year full-time at PARX. In Summer 2013, I decided to study again and moved to Mannheim. I kept working for the Swiss firm and later for the German subsidiary.

I finished my master’s degree in 2015 and moved back to Switzerland.

After returning to Switzerland I got more project management and technical architect tasks. I attended my first Dreamforce in 2015 and met my girlfriend. In winter 2017, I attended the CTA review board for the first time. I made it in all categories except 1. 😦
In the same year I decided to quite PARX and move on.

Deloitte and becoming a CTA

In April 2017 I started at Deloitte Digital Switzerland. A great place with incredible people. (I’m not sure if they want to get named… but the whole team was amazing.) I cannot say a bad word about Deloitte. It was a good place. Salesorce offered me to redo the one category of the CTA certification. I passed in May 2017 in London. The day before I attended the Salesforce Conference in London and took another photo with Sassy:

2017-11-01-PHOTO-00000010.jpg

 

Deloitte was a great place. However, it was time to move forward.

Accenture

In November 2017 I started at Accenture as a Manager. One of the first things I did in Accenture was going to my 2nd Dreamforce. As always a incredible experience. Accenture is a fantastic employer. I feel home at Accenture.

Next Steps

For me the last years have been amazing. I’m very thankful for what I have achieved.

What’s going to happen next?

  • Accenture is a fantastic employeer. This year I’m allowed to go there again.
  • I will marry the girl, I met at Dreamforce on August 30th.

Besides from that… let’s see what happens next..

Salesforce Certification Journey

One of the questions that comes up when I talk to colleagues that joined Salesforce Consulting recently is: “Which path should I take in my certification journey?”

When I started Salesforce the Paths were simple: Admin -> Advanced Admin, Developer -> Advanced Developer on top of that Salesforce introduced Service and Sales Cloud Consultants.

With the much richer ecosystem present today Salesforce as expanded and specialist even more. Today Salesforce offers kind of 3 or 4 major tracks:

On the Force Platform

  • The Developer / Architect Path
  • The Consulting Path with different specializations in the areas Service, Sales and Community (Not to forget CPQ)

In the Marketing Cloud

  • The Marketing Cloud Consultant Path
  • The Pardot Consulting Path

And for Comemrce

  • The Commerce Cloud Developer

Compared to some years ago the Salesforce landscape has changed and more certifications became available. I personally suggest to go one of the following routes:

Platform Consultant Journey

Salesforce-Consultant.png

Architect Journey

Architect-Journey.png

Marketer Journey

Marketer.png

Ecommerce Journey

Commerce-Cloud.png