<\/span><\/h2>\nTo begin, log in to the SAR mail system and navigate to the tab. From there, access your account and extend your trial if needed. Once complete, head to the inbox to verify test emails.<\/p>\n
SAR provides multiple ways to connect with your organisation\u2019s SMTP service:<\/p>\n
1. Using Your Organisation\u2019s SMTP Server<\/strong><\/p>\nNavigate to the Domains section.<\/p>\n
Add your organisational email domain.<\/p>\n
Configure SAR to send emails directly from this domain.<\/p>\n
2. Configuring the Sender Section<\/strong><\/p>\nEdit details one by one, such as the domain and credentials.<\/p>\n
The SMTP server will still be pinged, but the email will appear to come from your organisation\u2019s official address.<\/p>\n
3. Testing the SMTP Setup<\/strong><\/p>\nCopy and paste your credentials (e.g., Gmail username and password).<\/p>\n
Send a test email and verify delivery in your inbox.<\/p>\n
If successful, MFA (Multi-Factor Authentication) can be enabled using the configured account.<\/p>\n
If SAR blocks free services, you can generate OTPs through MailOSAR to complete the authentication process.<\/p>\n
<\/span>Expanding Beyond Email: SMS and Voice Integration in PingOne<\/strong><\/span><\/h3>\nSMTP isn\u2019t limited to just emails. SAR also supports SMS and voice call notifications.Organisations can integrate services like Tivoli or other internal communication tools, extending authentication beyond email.<\/p>\n
<\/span>Streamlining Authentication: PingOne with Google & Yahoo in Salesforce”<\/strong><\/span><\/h3>\nIn the ever-evolving landscape of web applications, ensuring seamless and secure user authentication is a must.<\/p>\n
Recently, we\u2019ve successfully configured Google\u2019s Gmail account as an identity provider (IdP) for a Salesforce application, and now it\u2019s time to test it out.<\/p>\n
The steps involved in setting up Google and Yahoo as identity providers, linking them with Salesforce, and introducing multi-factor authentication (MFA) to strengthen security.<\/p>\n
Along the way, we\u2019ll also touch on some advanced identity management techniques, such as password less and progressive profiling authentication.[\/et_pb_text][et_pb_text _builder_version=”4.9.7″ text_font=”Georgia||||||||” text_text_color=”#000000″ text_font_size=”22px” text_line_height=”1.9em” max_width=”800px” max_width_last_edited=”off|phone” custom_margin=”|||10%” custom_margin_last_edited=”off|desktop” text_font_size_tablet=”” text_font_size_phone=”” text_font_size_last_edited=”on|phone” text_line_height_last_edited=”off|phone”]<\/p>\n
<\/span>Step 1: Setting Up Google as an Identity Provider<\/strong><\/span><\/h3>\nA Gmail account is an identity provider for our application. After enabling the IdP and logging into the Single Sign-On (SSO) portal, we went to the Authentication and Policies Configuration section and created a new login policy.<\/p>\n
Once the login policy was in place, we edited it to include the Google IdP.<\/p>\n
At this stage, we added Google to the list of authentication providers and configured the necessary settings. With everything set up, we proceeded to test the login flow.<\/p>\n
<\/span>Step 2: Linking the Google Account to Salesforce<\/strong><\/span><\/h3>\nThe next phase was to access Salesforce using the Google account we had just configured. When attempting to log in, we encountered a prompt asking to link the Google account to the Salesforce user.<\/p>\n
This step is required only the first time, as linking the accounts enables seamless future access.<\/p>\n
After successfully linking the accounts, we were asked to enter the Google password. This first password is temporary and valid for the initial login.<\/p>\n
Once we changed the password, that password would be used for subsequent logins.<\/p>\n
Upon logging in again, the system prompted us for multi-factor authentication (MFA), adding an extra layer of security to the login process.<\/p>\n
This is where the experience becomes more secure, ensuring that users are verified with more than just a password.[\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row column_structure=”1_3,1_3,1_3″ _builder_version=”4.9.7″ _module_preset=”default” background_color=”#064399″ use_background_color_gradient=”on” background_color_gradient_start=”#0095f2″ background_color_gradient_end=”#7dbed8″ background_color_gradient_direction=”92deg” background_color_gradient_start_position=”35%” background_color_gradient_end_position=”80%” transform_scale=”73%|62%” transform_scale_linked=”off” transform_translate=”-53px|-50px” transform_translate_linked=”off” link_option_url=”https:\/\/cloudfoundation.com\/blog\/” link_option_url_new_window=”on”][et_pb_column type=”1_3″ _builder_version=”4.9.7″ _module_preset=”default”][et_pb_image src=”https:\/\/cloudfoundation.com\/blog\/wp-content\/uploads\/2023\/06\/SS_436-_Converted_-1.png” url=”https:\/\/cloudfoundation.com\/blog\/” url_new_window=”on” _builder_version=”4.9.7″ _module_preset=”default” transform_scale=”114%|112%” transform_scale_linked=”off” transform_translate=”25px|-4px” transform_translate_linked=”off” width=”98.1%” custom_margin=”|7px|||false|false”][\/et_pb_image][\/et_pb_column][et_pb_column type=”1_3″ _builder_version=”4.9.7″ _module_preset=”default”][et_pb_text _builder_version=”4.9.7″ _module_preset=”default” text_font=”Georgia|700|||||||” text_font_size=”23px” text_line_height=”1.3em” header_font=”Georgia|700|||||||” header_font_size=”21px” header_letter_spacing=”-1px” header_line_height=”2em” transform_scale=”171%|159%” transform_scale_linked=”off” transform_translate=”40px|44px” transform_translate_linked=”off” transform_origin=”70%|50%” z_index=”-161″ width=”100%” custom_margin=”|-215px||||” custom_padding=”|0px||||” link_option_url=”https:\/\/cloudfoundation.com\/blog\/” link_option_url_new_window=”on”]<\/p>\n
PingOne Training<\/strong><\/span><\/p>\n[\/et_pb_text][et_pb_button button_url=”https:\/\/cloudfoundation.com\/blog\/” url_new_window=”on” button_text=”Explore Course Content” _builder_version=”4.9.7″ _module_preset=”default” custom_button=”on” button_text_color=”#0C71C3″ button_bg_color=”#FFFFFF” button_font=”|700|||||||” transform_translate=”64px|65px” transform_translate_linked=”off”][\/et_pb_button][\/et_pb_column][et_pb_column type=”1_3″ _builder_version=”4.9.7″ _module_preset=”default”][et_pb_image src=”https:\/\/cloudfoundation.com\/blog\/wp-content\/uploads\/2019\/06\/logo_resize_color.png” url=”https:\/\/cloudfoundation.com\/blog\/” url_new_window=”on” _builder_version=”4.9.7″ _module_preset=”default” transform_translate=”-36px|0px” transform_translate_linked=”off” custom_margin=”|||178px||”][\/et_pb_image][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.9.7″ background_size=”initial” background_position=”top_left” background_repeat=”repeat”][et_pb_column type=”4_4″ _builder_version=”3.25″ custom_padding=”|||” custom_padding__hover=”|||”][et_pb_text _builder_version=”4.9.7″ text_font=”Georgia||||||||” text_text_color=”#000000″ text_font_size=”22px” text_line_height=”1.9em” max_width=”800px” max_width_last_edited=”off|phone” custom_margin=”|||10%” custom_margin_last_edited=”off|desktop” text_font_size_tablet=”” text_font_size_phone=”” text_font_size_last_edited=”on|phone” text_line_height_last_edited=”off|phone”]<\/p>\n
<\/span>Step 3: Handling Yahoo Accounts with Google Credentials<\/strong><\/span><\/h3>\nFor users who have Yahoo accounts, there\u2019s a slight variation in the process. After linking the Google account to Salesforce, we attempted to log in to a Yahoo account.<\/p>\n
Here, instead of a new password, we used the Google password for access.<\/p>\n
However, since we\u2019re authenticating with Google, we couldn\u2019t simply log in with the system\u2019s default credentials.<\/p>\n
To resolve this, we had to go back to the external identity providers section and adjust the settings for Yahoo.<\/p>\n
<\/span>Step 4: Enabling the Yahoo Identity Provider<\/strong><\/span><\/h3>\nWe added Yahoo as an additional identity provider. This involved navigating to Yahoo\u2019s developer tools to obtain a client ID and secret.<\/p>\n
We used this information to configure the integration in the Salesforce application.<\/p>\n
Once the application was updated with Yahoo\u2019s credentials, we ensured the identity provider was enabled in the settings.<\/p>\n
After saving these changes, we tested logging into Salesforce again, now with the ability to authenticate via both Google and Yahoo accounts.[\/et_pb_text][et_pb_text _builder_version=”4.9.7″ text_font=”Georgia||||||||” text_text_color=”#000000″ text_font_size=”22px” text_line_height=”1.9em” max_width=”800px” max_width_last_edited=”off|phone” custom_margin=”|||10%” custom_margin_last_edited=”off|desktop” text_font_size_tablet=”” text_font_size_phone=”” text_font_size_last_edited=”on|phone” text_line_height_last_edited=”off|phone”]<\/p>\n
<\/span>Step 5: Advanced Authentication Policies<\/strong><\/span><\/h3>\nWhen configuring external IdPs, such as Google and Yahoo, advanced authentication policies can enhance both security and the user experience.<\/p>\n
These include the identifier first policy and password less authentication.<\/p>\n