SSO on iOS/iPadOS

Use this page to understand how Clever SSO behaves on iOS and iPadOS and choose the right implementation pattern for your app.

How Clever SSO works on iOS and iPadOS

The Clever iOS app is primarily used for authentication with a Clever Badge. It does not include the iOS Clever Portal experience.

If a user is not signing in with a Clever Badge, they are redirected to Safari to authenticate into the Clever Portal with their identity provider, such as Google, Azure, or Clever.

After the user signs in to the Clever Portal and selects your application:

• if your app’s redirect URL is registered as a Universal Link, iOS opens your native app
• if your redirect URL is not registered as a Universal Link, the user is sent to your web experience in the browser

To learn more about the end-user experience, see For Clever Admins: iOS devices & the Clever app.

🚧

Unsupported iOS versions

The Clever iOS application requires:

• iOS 12.0 or later
• iPadOS 12.0 or later

The Clever iOS app is not required for SSO on iOS devices. It is primarily used to support Clever Badges.

SSO patterns on iOS and iPadOS

If you have a native iOS app

Use Universal Links. This is the recommended implementation pattern for native iOS apps.

For implementation details, read iOS/iPadOS - Native Apps.

If you do not have a native iOS app but support mobile browsers

You do not need additional iOS-specific app handling.

Make sure your primary redirect URL is mobile-friendly, or detect iOS devices and redirect users to a mobile-optimized experience.

If your application does not support iOS users

Contact Clever Support through the Help Center chat so Clever can disable logins from the iOS application for your integration.

Also make sure your primary redirect URL detects iOS devices and shows a page that explains iOS is not supported. This helps route users who try to sign in from mobile web.