Can I use custom objects as the identity source?

Yes, you can use custom objects as the identity source provided they include identity attributes such as username or email that can be mapped to the SSO assertion.

What authentication protocols are supported?

Our Salesforce SSO connector supports SAML, OAuth, and OpenID Connect, giving flexibility during Salesforce SSO integration based on application compatibility and security requirements.

When should we choose Salesforce as the IDP instead of an external IDP?

Choose Salesforce as the IDP when you want to enable SSO for Salesforce Users, Contacts, Leads, or Custom Objects without purchasing additional Salesforce user licenses. Our Salesforce SSO Connector turns these records into full-fledged IDP users and centralizes identity management in Salesforce.

Salesforce as IDP
SSO for Contacts, Accounts, and Custom Objects

SSO for Contacts, Accounts, and Custom Objects

Get it on AgentExchange

Schedule Meeting with Expert

Why Setting Up Salesforce SSO for External Users is Challenging

Time-Consuming Administration

Managing external users, access permissions, and authentication settings can require significant ongoing effort.

Higher Costs at Scale

Providing secure SSO for large numbers of external users may require additional Salesforce products, licenses, or infrastructure.

Limited Login Flexibility

Supporting different authentication methods and external Identity Providers may require additional configuration or tools.

Complex Setup Process

Setting up external SSO connections often involves configuring protocols, user mappings, and application settings, which requires technical expertise.

How can Salesforce act as an Identity Provider?

With the miniOrange Login using Contacts, Accounts, and Custom Objects solution, you can turn Salesforce into a fully functional Identity Provider for any Salesforce standard or custom object.

Contacts as Identity Source

Accounts as Identity Source

Leads as Identity Source

Custom Objects as Identity Source

Contacts as Identity Source

Contact SSO allows login into other applications using the Salesforce contact records, without creating a new Salesforce user.

Key Features of Our Login using Contacts, Accounts, and Custom Objects Solution

Manage who gets access, how they log in, and when access changes, all through the Salesforce SSO login.

Salesforce as IDP

Configure Salesforce IDP to authenticate users and issue identity assertions to external applications, and allow users to access connected Service Providers (SPs) with their Salesforce credentials.

Custom Salesforce Objects

Authenticate users from Salesforce Contacts, Leads, Accounts, or Custom Objects as identity sources or recipients of federated login.

Real-Time User Provisioning

Automatically create, update, or delete users in connected applications as Salesforce records change.

Protocol Support

Supports SAML 2.0, OAuth 2.0, and OpenID Connect (OIDC) to ensure compatibility with a wide range of enterprise and SaaS applications.

Attribute and Role Mapping

Map Salesforce fields to SAML or OpenID Connect attributes. Control roles, permissions, and access in connected applications through Salesforce SSO login assertions.

IDP and SP-Initiated SSO

Allow users to start authentication either from Salesforce or directly from the client application's login page.

MFA Enforcement

Apply Salesforce MFA policies across connected applications with support for 29+ authentication methods.

Audit and Reporting

Track every Salesforce SSO login event, assertion issuance, and user access using Salesforce object history, logs, or custom dashboards.

Connect Salesforce Identity Provider to Every External Application

Once Salesforce is set up as an IDP, users get SSO access to JIRA, Shopify, Slack, HubSpot, QuickBooks, SharePoint, and many more external applications out of the box.

Salesforce Single Sign On | Salesforce as Identity Provider | QuickBooks

Single Sign On for Salesforce | Salesforce as Identity Provider | Shopify

Single Sign On for Salesforce | Salesforce as Identity Provider | WordPress

Salesforce Single Sign On | Salesforce as Identity Provider | Jira

Single Sign On for Salesforce | Salesforce as Identity Provider | SharePoint

Salesforce Single Sign On | Salesforce as Identity Provider | Slack

Salesforce Single Sign On | Salesforce as Identity Provider | HubSpot

Salesforce Single Sign On | Salesforce as Identity Provider | MS Teams

Don't see your application above? Contact us, and we will handle the integration for you.

Request an Integration

Here is Everything You Need to Make the Best Decision

Native Salesforce SSO vs. miniOrange Login with Contacts, Accounts, and other Custom Objects

Parameter

Cost

Scalability

Who Can Log In

Setup and Support

Fixed $2/user/month pricing based on your user count.

You need just one license to get started. As your user base grows, simply upgrade your plan to cover more users.

Contacts, Leads, Accounts, Cases, and Custom Objects can all log in to connected Service Providers (SPs).

Easy to set up on your own. Documentation, 24/7 engineer support, and free consultations are also available across every time zone.

A Salesforce Identity license costs $5/user/month, or you get 100 complimentary licenses with Professional / Enterprise / Unlimited / Performance Editions.

Costs increase exponentially with each additional user, as each external user requires a separate Salesforce license.

Only licensed Salesforce users can log in to connected SPs.

Some technical configuration is needed before everything works as expected. Standard Salesforce support only.

How miniOrange Login using Contacts, Accounts, and Custom Objects Works

Start using Salesforce as an Identity Provider for every external application in four simple steps.

1 Install miniOrange Package

Install the miniOrange Login using the Contacts, Accounts, and Custom Objects package from the AppExchange in your Salesforce instance.

2 Set Salesforce as an IDP

Enable SAML, OAuth/OIDC, or JWT and select the identity store, such as Users, Contacts, Leads, Accounts, or a Custom Object.

3 Configure Client Apps

Register client applications with metadata and assertion consumer URLs, then map Salesforce fields and roles to required user attributes.

4 Test and Monitor

Verify authentication flows end-to-end and monitor SSO login activity, MFA events, and provisioning status in real time.

Reduced Salesforce Licensing Costs

Authenticate Contacts, Leads, Accounts, and Custom Objects through Salesforce SSO without buying a full Salesforce license for every external user.

Easy Compliance Reporting

Track every login, provisioning action, and MFA verification inside Salesforce and export reports for SOC 2, HIPAA, and GDPR audits.

Zero Infrastructure Maintenance

Install the miniOrange Login using the Contacts, Accounts, and Custom Objects solution from AppExchange and run everything inside Salesforce, with no external servers or middleware to set up or manage.

24/7 Customer Support

Get help with setup, configuration, and custom integrations any time you need it. Our technical support team works 24/7 across every time zone so your deployment never stalls.

Frequently Asked Questions

Contact Us

Technical

Absolutely. Salesforce as Identity Provider works for Contacts, Leads, Accounts, and Custom Objects too, not just licensed Salesforce Users. No extra licenses are needed for Salesforce SSO for external applications or connected service providers.

Salesforce SSO for external applications works with WordPress, Shopify, JIRA, Confluence, WooCommerce, and any app that supports SAML, OAuth, or OpenID Connect. Do not see yours? Just reach out, and we will sort it out.

Yes, completely automatically. Salesforce user provisioning means that when you add or deactivate a record in Salesforce, access in connected apps updates right away. No manual work needed.

It works across every connected app. Salesforce MFA SSO applies your existing MFA settings to all applications automatically. Salesforce secure login supports 29+ verification methods, so your users stay protected at every login.

Much more affordable, yes. Native Salesforce SSO charges $5 per user every month. Our Login using Contacts, Accounts, and Custom Objects solution uses tier-based pricing, so your costs stay predictable and manageable no matter how many users you have.

Requirements and Compatibility

Our Salesforce SSO Connector supports Enterprise and Unlimited editions, which include identity features required for Salesforce Single Sign On.

Our Salesforce SSO AppExchange Connector is installed as a managed package from AppExchange directly on your Salesforce instance, making the installation process quick and straightforward..

Yes. Service Providers (SPs) must support SAML 2.0 or OpenID Connect (OIDC) in order to integrate with Salesforce as an IdP.

You need Salesforce administrator access to configure Connected Apps, upload certificates, and set SSO policies.

Salesforce Identity licenses are typically required when authenticating external users. This depends on how users are modeled and how Salesforce SSO configuration is implemented.

We'll Reach Out to You at the Earliest!

Salesforce as IDP
SSO for Contacts, Accounts, and Custom Objects

SSO for Contacts, Accounts, and Custom Objects