Overview
When you request a Single Sign-On (SSO) configuration for your iObeya platform, we ask several questions to understand your needs.
These questions help us:
align authentication with your internal rules
secure access to your platform
define how accounts are created
avoid conflicts between SSO and local login
apply the right password and security settings
We guide you through each option so that your authentication setup matches your needs.
Your answers help us configure iObeya ID correctly and explain the main capabilities available in your authentication setup.
Defining How Accounts Are Created and Managed
To understand how users access the platform, we ask:
Do you want users to self-register on the platform?
Do you want to keep email verification?
Do you want users to retrieve a forgotten password from the login page
These options affect how users access iObeya when they are not signing in through SSO.
Confirming your SSO Requirements
To prepare your SSO integration, we ask:
Do you have an SSO system that needs to be connected to iObeya?
Do you want users to sign in only through SSO?
Do you need several SSO connections for different groups?
If SSO is not used or not exclusive, we ask:
How do you want new users to access iObeya?
Do you need access to iObeya ID to create accounts manually when required?
Adjusting Local Login Settings When Available
If local login is enable on your platform, we also ask:
Do you want a custom password policy?
Do you want to add Multi-Factor Authentication for local accounts?
Do you want users to sign in with a username instead of an email?
Do you want to update the list of trusted email domains used for registration?
These settings define how secure and flexible the local login method are.
Managing Mixed Login Methods
If your platform uses SSO, local login and password reset at the same time, we ask one more question.
When a user account is linked to an external identity provider:
Do you want to prevent this user from signing in with the local login form?
This avoids conflicts between SSO accounts and local accounts and ensures consistent behavior.