—
Remedyforce Onboarding Services
August 2015
Brian Zentner
Remedyforce Tech Talk:
User Creation and Authentication
Agenda
• Overview of User Creation methods and User
Authentication
• How do I Create and Maintain my users in
Remedyforce?
• How do my users Authenticate into
Remedyforce?
• What is best for my implementation of
Remedyforce?
• Final Thoughts
—01
How to Create and Maintain
Users in Remedyforce
What is a user in Remedyforce?
Remedyforce utilizes the built in
functionality of Salesforce to manage
users. Every user is identified by a
username, a password, and a single
profile. Together with other settings, the
profile determines what tasks users can
perform, what data they see, and what
they can do with the data.
Salesforce User Profile
Salesforce User Profile
User Creation Options
• Manual
• Automated
– OneLogin
– Pentaho
—02
User Authentication Methods
for Remedyforce
Overview of Authentication in
Salesforce
How are log in credentials
created?
What types of
authentication methods
are available?
Where do users log in?
Credential Creation
• Credentials are generated automatically during
user creation
• Credentials are in the format of an email
address
• Credentials must be unique, across all
Salesforce organization instances
Native Salesforce Authentication
• Provided by Salesforce
• No development required
• Access to authentication
screen from any internet
connection
Single Sign-On Methods
• Federated authentication
user SAML
• Delegated Authentication
integration with LDAP
• Using an authentication
provider
Single Sign-On Implementation
Best Practices
• Delegated Authentication
• Federated Authentication using SAML
• Authentication Providers
—
Authentication and User
Maintenance in Remedyforce
03
How to Choose
User Creation and Maintenance
Considerations
Complexity of User-base
Time Investment
Infrastructure
Technical Skill of Staff
Security Policies
User Authentication Method
Considerations
Number of Salesforce Organizations
Types of Devices Used
Needs of your Users
User Locations
—04
Conclusion
Extra Resources
Remedyforce Communities
https://communities.bmc.com/community/bmcdn/bmc_remedyforce/
Salesforce Single Sign-On
https://login.salesforce.com/help/pdfs/en/salesforce_single_sign_on.pdf
OneLogin
https://www.onelogin.com/partners/app-partners/remedyforce-sso
Pentaho
http://community.pentaho.com/projects/data-integration/
—
Bring IT to Life.™
Thank You

User Creation and Authentication in Remedyforce

Editor's Notes

  • #2 Thank you Carol/Olivier. Hello everyone, as mentioned, my name is Brian Zentner. I am a Sr Associate Consultant with BMC Remedyforce Onboarding Services. I am very happy to be here today to discuss User Creation and User Authentication in the BMC Remedyforce Environment…..
  • #3 General Agenda: 1 Minute Overview: 4 Minutes Create and Maintain: 10 Minutes Authentication: 5 Minutes Best options: 20 Minutes Final Thoughts: 3 Minutes
  • #4 Lead in: 1 min Let’s begin with an overview of what a user is and how users are created and maintained in your environment. As a Remedyforce Administrator, your time is better utilized managing the application not……..
  • #5 Overview of a user: (Talking Points) – 2 mins Contains Demographic info Contains Security info (Profiles & Roles) Explain Profiles and Roles Misc Information (Manager, App licenses, VIP, Manager, Etc)
  • #6 User profile layout ( Explain fields and process ): Highlight: mandatory fields; BMC specific fields, Profiles, Roles, User License
  • #7 User profile layout ( Explain fields and process ): Highlight: mandatory fields; BMC specific fields, Profiles, Roles, User License
  • #8 User profile layout ( Explain fields and process ): Highlight: mandatory fields; BMC specific fields, Profiles, Roles, User License
  • #9 Let’s begin with an overview of how users are created in your environment and how those users log in.
  • #10 Credentials are created when the user is created. Authentication methods: Native Salesforce Auth; Delegated Authentication; Federated Authentication; Salesforce Native: Simple login at login.sf.com Delegated Auth: A SSO solution, utilizes a web service call to determine if a user has logged into a web site (IE: Intranet Portal) Federated Auth: A SSO solution, utilizes SAML (Security Assertion Markup Language) Auth provider: A SSO solution, utilizing a Pre-integrated service from a branded Identity Service Where a user logs in is dependent on which Auth method used. For Native: login.salesforce.com OR test.salesforce.com
  • #12 User login.salesforce.com for prod, test.salesforce.com for sandbox
  • #13 Federated Auth: Allows you to send authentication between unrelated Web Services. Allows sign on from Client applications. Enabled by default in the Salesforce org. Delegated Auth: Allows integration with an auth of your choice: integrate with LDAP, auth with security token instead of password. Set by permissions not by org level (can have some user auth with Delegated auth and some with SF standard auth.
  • #18 User Creation Authentication Methods Best Practices Implementation Considerations
  • #19 HyperLinks to Salesforce and Remedyforce resources
  • #20 BMC Remedyforce has an extremely active user community where you can get answers to additional questions on this topic. We encourage you to take a look at bmc.com/communities.