Skip to main content

Setup my domain on Salesforce


Currently I am setting up SSO (single sign on) for my Salesforce environment. As part of this setup, i needed to setup a domain for the environment first. It is a very simple setup in Salesforce.

You may want to setup a domain for your environment for different reasons -
1. Add some branding to your environment (your own environment specific url, a branded login page with your company logo, etc)
2. Security reasons - setup your own login url and force your users to use this. It will prevent access from the standard salesforce login url.
3. Add single sign on for your org with required authentication capabilities

Below are the steps I followed for setting up a My Domain url in Salesforce -


  • Navigate to Setup -> Domain Management -> My Domain
  • Populate a unique value in the textbox for the domain name. Choose a value that will make sense to your company and environment. An example screenshot below -

  • Click the register Domain button. The registration takes some time. You will see a message as shown below first -


  • Once the domain gets registered, refreshing the page will indicate the same. At this point you can test your login by trying out the new domain you created - 

you should be able to login by accessing your domain url successfully.
To test you can click the "Click here to login" button in the My Domain setup page.

Note: Setting up a my domain does not prevent users from being able to login from the standard salesforce login url - https://login.salesforce.com. You will prevent that in a step further below.
  • At this point, you can do some branding for your domain. Click the Edit button in the Authentication Configuration section of the My Domain page
  • In the resulting page, choose the following to do your branding - 
    • Logo for your company
    • background color of the login page
    • Right Frame URL - choose what you want to show on the right hand side on the login page
    • Authentication Service (see below)
  • Authentication Service - You can leave this as Login Page to allow users to login with their salesforce username and password. If you wish to configure your domain for Single Sign On, you will have to choose it here. Please see my next few blogs for figuring out how to setup SSO in Salesforce.
  • Now you are ready to deploy this to your users. Note this is not reversible. For this click the "Deploy to Users" button.
  • After deploying to users, you can choose to prevent users from logging in from the standard Salesforce login. For doing this, after you deploy to users, click the Edit button on the My Domain Settings section -


Now your domain is ready and should be available for use by your users. Enjoy!



Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

Workaround to bypass Salesforce SSO

One of the best practices for implementing Single Sign On for your Salesforce org is always ensure there is a way your System administrator can login via the standard login page side-stepping the SSO configuration.  Reason for this is if ever something goes wrong with your Idp provider's service and the SSO authentication responses are not coming as expected, all your users are unable to login. That is, if you have setup your My domain to prevent logins via standard Salesforce login urls (login.salesforce.com). This includes the System administrator as well. Only if your system administrator can somehow login, then he or she can disable the SSO settings for your domain and allow login via the normal login page as a temporary measure. What do you do in such a situation? Well Salesforce has built a workaround for this which is not well documented anywhere (probably for a good reason :) ). I found out about it from a colleague at work. If your my domain url is - https://Com...
42 comments
Read more

DBAmp for Salesforce - salesforce integration for SQL Server DBAs

Recently i got the opportunity to explore a tool called DBAmp for integration with Salesforce. I found it to be a very useful tool which will help with any data manipulation requirements in Salesforce. Following are my learnings from the exercise. Hope it helps any of you who may need to work with this tool -  DBAmp is a SQL Server package that can be used to integrate with Salesforce. The site where this software is available is - http://www.forceamp.com/ Overview: It essentially installs on top of an existing SQL Server database and provides an OLE DB connector that can be used to connect to Salesforce. Behind the scenes, it executes API calls against Salesforce for any SQL server command it receives. Thus we can create a connection in SQL server to Salesforce org and pull data into tables in the database just as if we are querying against Salesforce tables directly. Use cases for DBAmap + Salesforce: Many use cases exist for using this tool against Sales...
7 comments
Read more

Asynchronous Apex webservice callout - Continuation pattern

In my last two posts, we went through a basic example of consuming an external web service in Salesforce to generate a stub class and then using that stub class to call the webservice from a visualforce page controller. Integrating Salesforce with SOAP webservice - Apex callout Integrating Salesforce with SOAP webservice - Apex callout part 2 In the above example, our callout was synchronous. The user as well as our code (system resources) are going to wait for the webservice to reply and our code to process the response prior to be able to do anything else. If the external webservice responds within 1-2 seconds, no harm done. This should be fine. However there are chances you will encounter webservices in business scenarios that will take longer to respond. This may be because they have to do a significant amount of work prior to responding back to Salesforce. Maybe they process huge number of transactions and during peak loads, their response is slower. All possible scenar...
8 comments
Read more