A Salesforce Certified Identity and Access Management Designer assesses the architecture environment and requirements and designs sound and scalable technical solutions on the Force.com platform that meet Single Sign On (SSO) requirements. The architect has experience communicating solutions and design…
We’ll look at several core OAuth flows relevant to Salesforce. Join us to learn about Identity Flows OAuth 2.0. User interaction No user interaction Authorisation Code + Secret (Web Server) Implicit Grant (User-Agent) Authorization Code + PKCE JWT Bearer SAML…
In this post we will talk about How to Setup Okta Single Sign-On (SSO) with Salesforce. Okta connects any person with any application on any device. Okta enables you to provide Single Sign On (SSO) access to cloud, on-premises, and mobile applications. You…
Allows the client to authenticate using the user’s username and password and a protected secret. Use the username-password authentication flow to authenticate when the consumer already has the user’s credentials. Avoid using this flow because you have to send a…
In this post we will talk about Salesforce naming conventions best practices and how to write a clean code. Naming convention in Salesforce is a rule to follow as you decide what to name your identifiers like class, variable, constant, method,…
Join us and learn about it. The governance dilemma for Salesforce projects makes Salesforce special compared to other platforms. Why have many Salesforce projects struggled with quality despite governance? The CTA’s role in defining and implementing a Salesforce governance model…
Secure server-to-server integration without real time user involvement. Client specifies user in a JSON web token (JWT) or SAML format XML assertion and proves its own identity by appending a signature. JWT Bearer token flow is Ideal for application which…
This post will discuss Authorisation Code with PKCE Flow(for browser, mobile & desktop apps). A variation of auth. Code flow for clients that can’t protect a global secret. Better security than implicit grant / user-agent for similar use cases. Additional…
A simpler flow for clients that should not hold a global secret (e.g., distributed apps) but can be trusted with the per-user access token. This flow is recommended when you build mobile or desktop application and your application can be distributed…
Allows apps with a secure client server (one which can protect a secret or private key) to access protected resources. This flow is mainly used by applications hosted on web server. If external application is trusted one and hosted on secure…