Skip to main content
Connect June with your identity provider to enable single sign-on (SSO), automated user provisioning, and seamless user lifecycle management.

Supported Identity Providers

Integration Benefits

Single Sign-On (SSO)

  • Seamless Login: Users access June with their existing credentials
  • Reduced Password Fatigue: Eliminate separate June passwords
  • Enhanced Security: Leverage your IdP’s security features
  • Compliance: Meet enterprise authentication requirements

Automated User Management

  • User Provisioning: Automatically create June accounts
  • Attribute Sync: Keep user information up-to-date
  • Role Assignment: Map IdP groups to June roles
  • Deprovisioning: Disable access when users leave

Enhanced Security

  • Multi-Factor Authentication: Leverage existing MFA policies
  • Conditional Access: Apply context-aware access controls
  • Audit Trail: Comprehensive logging of authentication events
  • Risk-Based Authentication: Adaptive security based on user behavior

Quick Start Guide

1. Choose Your Identity Provider

Select your organization’s primary identity provider:
1

Enterprise Identity Providers

  • Okta: Comprehensive identity management platform
  • Microsoft Entra ID: Azure Active Directory for enterprise
  • Google Workspace: Google’s identity and productivity suite
2

Generic Standards

  • SAML 2.0: Industry standard for SSO
  • SCIM 2.0: Standard for user provisioning
  • Custom Integration: API-based integration for other providers

2. Prepare Integration Requirements

All identity provider integrations require:
  • Administrative Access: Admin privileges in your IdP
  • June Admin Rights: Organization admin permissions in June
  • User Attributes: Understanding of user data structure
  • Group Structure: Knowledge of existing groups and roles

3. Follow Provider-Specific Guide

Click on your identity provider above for detailed instructions including:
  • SSO configuration steps
  • User provisioning setup (SCIM)
  • Group and role mapping
  • Testing and troubleshooting

Common Integration Features

User Attributes

Standard attributes synced across all providers:
AttributeDescriptionRequired
EmailPrimary identifier and loginYes
First NameUser’s given nameYes
Last NameUser’s family nameYes
DepartmentOrganizational departmentNo
Job TitleUser’s role/positionNo
ManagerReporting relationshipNo
Employee IDUnique employee identifierNo

Role Mapping

Map IdP groups to June roles:
  • Organization Admin: Full system access
  • IT Manager: Device management and reporting
  • IT Technician: Basic device operations
  • Department Manager: Department-specific access
  • Team Lead: Team device oversight
  • End User: Personal device access only
  • Compliance Officer: Audit and compliance access
  • Finance Manager: Cost and budget reporting
  • Security Analyst: Security monitoring access

Provisioning Actions

Supported SCIM operations:
  • Create: Automatically create new user accounts
  • Read: Retrieve user information and status
  • Update: Sync changes to user attributes
  • Delete/Deactivate: Disable access for departing users

Authentication Methods

SAML 2.0 SSO

Benefits of SAML integration:
  • Industry Standard: Widely supported protocol
  • Secure: Cryptographically signed assertions
  • Flexible: Supports various authentication flows
  • Metadata Exchange: Simplified configuration

OAuth/OpenID Connect

Modern authentication features:
  • API Access: Secure API authentication
  • Token-Based: Stateless authentication tokens
  • Scope Control: Granular permission management
  • Refresh Tokens: Long-lived authentication sessions

Directory Sync

Direct directory integration:
  • LDAP/Active Directory: Traditional directory services
  • API Integration: Modern REST API connections
  • Real-Time Sync: Immediate user updates
  • Batch Processing: Efficient bulk operations

Best Practices

Security

  • Principle of Least Privilege: Grant minimum required access
  • Regular Audits: Review user access and permissions periodically
  • MFA Enforcement: Require multi-factor authentication
  • Session Management: Configure appropriate session timeouts

User Management

  • Consistent Naming: Use standard naming conventions for groups
  • Automated Lifecycle: Leverage SCIM for user provisioning
  • Department Alignment: Align access with organizational structure
  • Regular Cleanup: Remove unused accounts and permissions

Integration Health

  • Monitor Sync Status: Track provisioning success rates
  • Certificate Management: Monitor SAML certificate expiration
  • Error Handling: Set up alerts for authentication failures
  • Performance Monitoring: Track login times and user experience

User Lifecycle Management

Onboarding

  1. User Created: New user added to identity provider
  2. Automatic Provisioning: June account created via SCIM
  3. Role Assignment: Groups mapped to appropriate June roles
  4. Device Assignment: Devices allocated based on department/role
  5. Access Verification: User can log in and access assigned resources

Updates

  1. Attribute Changes: Department, role, or manager updates
  2. Automatic Sync: Changes propagated to June
  3. Permission Updates: Access adjusted based on new attributes
  4. Device Reassignment: Device access updated if needed

Offboarding

  1. User Deactivated: Account disabled in identity provider
  2. Automatic Deprovisioning: June access immediately disabled
  3. Device Recovery: Devices marked for recovery
  4. Data Security: Ensure secure handling of departing user data

Troubleshooting

Common Authentication Issues

  • Verify SAML configuration and metadata
  • Check certificate validity and signing
  • Ensure user is assigned to June application
  • Review attribute mapping requirements
  • Verify SCIM endpoint and authentication
  • Check required user attributes are present
  • Review API rate limits and quotas
  • Validate user attribute mappings
  • Check group membership and role mappings
  • Verify June role configuration
  • Review department-based access rules
  • Test with different user profiles

Getting Help

  • Provider-Specific Guides: Detailed troubleshooting in individual guides
  • June Support: Contact support for integration assistance
  • Community Resources: Join user forums and discussions
  • Professional Services: Expert help for complex configurations

Compliance and Auditing

Audit Trail

  • Authentication Events: Track all login attempts and outcomes
  • Provisioning Activity: Log user creation, updates, and deletions
  • Permission Changes: Record role and access modifications
  • Integration Health: Monitor sync status and errors

Compliance Features

  • SOC 2 Compliance: Meet security and availability requirements
  • GDPR Support: Handle user data according to privacy regulations
  • Industry Standards: Support for healthcare, finance, and other regulated industries
  • Data Retention: Configurable retention policies for audit data

Next Steps

After setting up your identity provider integration:
Test all identity provider changes in a development environment before applying to production to avoid user access disruptions.
Identity provider integrations typically sync user data within 15 minutes. Large user bases may require additional time for initial synchronization.
I