FieldFX Reviews and Details

Social recommendations and mentions

• How to sync your MySQL database with Salesforce in Docker using Boomi

  A Salesforce Security Token is required to connect to your Salesforce application. To obtain your token, log in to your Salesforce account, click on your avatar, and navigate to settings. This process ensures a more secure connection by adding an extra layer of authentication. - Source: dev.to / over 2 years ago

• Single-Sign-On with Okta - Do we still need to have Salesforce MFA enabled?

  So if we login via login.salesforce.com then we will continue to see the MFA requirement? Source: over 3 years ago

• SSO not appearing in My Domain

  I assume you have my domain enabled in the Production org? Maybe you need to turn on prevent login from login.salesforce.com? Source: over 3 years ago

• Creating Custom API Endpoints in Salesforce with Apex

  With our token in hand, we select the login SoapBinding in SoapUI. Ensure you have the correct URL depending on your org. If you just signed up for a developer account, the URL should be https://login.salesforce.com. If you are testing this in a Sandbox, then the URL should be https://test.salesforce.com. Ideally, the generated Enterprise WSDL will already have the correct URL. - Source: dev.to / over 3 years ago

• Resetting user passwords

  I'm a program manager leading our MFA integration for our users. Part of that is logging them out and having them authenticate via login.salesforce.com. However, most of them don't remember their passwords. When I try resetting them, their reset URL just takes them into an already logged in instance of SFDC. Others are receiving an error that they can't reset their password because they don't have a security... Source: over 4 years ago

• SSO Enabled - Users can still login with username and password

  1: Disable direct logins through login.salesforce.com. Source: over 4 years ago

• SSO Enabled - Users can still login with username and password

  "Prevent login from https://login.salesforce.com" has been checked per the document I linked in the original post. Source: over 4 years ago

• SSO query

  We have "Disable login with Salesforce credentials" checked in "Single Sign-On Settings," but only enable "is single sign on enabled" for non-admin users (via a profile and/or permission set). That allows admins to use both SSO via our "my domain" url and their Salesforce credentials via https://login.salesforce.com" while all non-admin users are limited to SSO via the my domain URL. Source: over 4 years ago

• Turning On Salesforce MFA For Admins, Part 2

  Checked "Prevent login from login.salesforce.com" (in My Domain settings). Source: over 4 years ago

• Turning On Salesforce MFA For Admins

  So what I am going to do is have our non-SSO users (such as admins) log in from mycompanyname.my.salesforce.com/?login 9with MFA enabled). Because this URL is more customized, it's my understanding that using it for login is more secure than using login.salesforce.com. Most of our users do prefer the convenience of SSO, so I am keeping "Login Form" unchecked, to speed up the process. And most of them did set up a... Source: over 4 years ago

• Turning On Salesforce MFA For Admins

  - Assigned myself a perm set with the setting "Multi-Factor Authentication for User Interface Logins" - Connected to the Salesforce Authenticator app - Checked "Prevent login from login.salesforce.com" (in My Domain settings) - Checked "Disable login with Salesforce credentials" (In SSO settings) - Enabled SSO at the profile level for all profiles except my own. Source: over 4 years ago

• How to enable person accounts in dev org?

  Sfdx force:org:create -f config/project-scratch-def.json ERROR running force:org:create: InvalidPackageDirectory What can be the reason? Package-json file: { "packageDirectories": [ { "path": "force-app", "default": true }, { "path": "unpackaged" }, { "path": "utils" } ], "namespace": "", "sfdcLoginUrl": "https://login.salesforce.com", "sourceApiVersion": "52.0" }. Source: over 4 years ago

• Types of Authentication - Standard Login vs Connected App

  I am creating a chrome app right now and am wondering why I wouldn't just run a standard OAuth flow requiring the user to submit their username and password directly to login.salesforce.com to connect their Salesforce account rather than creating a connected app. Source: over 4 years ago

• SAML SSO question

  The way we have done it is tie the SSO to a permission set. Assigned that to everyone except system admins and anyone else not in domain. This allows us to login via login.salesforce.com only for the users without the permission set. Source: over 4 years ago

• Updating My Domain - Deal with Password Managers/User Experience

  I think you are potentially overthinking it... https://test.salesforce.com would still resolve to your sandbox and https://login.salesforce.com too in terms of Prod. Source: almost 5 years ago

• Postman Collection for Salesforce: Mock Servers and Code Snippets

  Once you have a Salesforce org to work with, switch back to Postman and select the Salesforce API Collection again. In the Variables tab, ensure the URL parameter has the Current Value set to https://login.salesforce.com. In the Authorization tab, click on Get New Access Token. Log in to Salesforce with the username and password you created when setting up your account. When prompted, allow access for Postman. - Source: dev.to / almost 5 years ago

• Trailheads without a Prod environment

  I feel like I'm missing something obvious here. I'm going through the Trailheads and am occasionally prompted to login to https://login.salesforce.com, for example to complete this AppExchange module. I don't personally have a Salesforce account (current job doesn't have Salesforce). I have a Trailhead account and multiple playgrounds. What am I missing here? Source: almost 5 years ago

• How to authorize an Integration users when Login Credentials are disabled?

  We have recently enabled SSO with Azure for our users in our production org and we are running into an issue with our integration users not being able to authorize access since the Login Form was removed (redirects to Azure) and https://login.salesforce.com was also disabled. We have to remove those security restrictions every time to authorize our 3rd party apps. Has anyone have to deal with this before and how... Source: almost 5 years ago

• Login attempts not registering?

  Personally I always use login.salesforce.com to log into my org, I had no idea it might be an issue. I will check her login URL, thanks! Source: about 5 years ago

• Question on the upcoming MFA requirements and SSO

  Oh handy tip on the "?login" part. It would be good to disable login.salesforce.com like you said to make the end user experience smoother. We'll check into that link, some good stuff there. Source: about 5 years ago

• Objects and Database Tables in Salesforce

  First, go to https://login.salesforce.com/. - Source: dev.to / about 5 years ago