In addition to logging into Iteratively with a username and password, users can also log in with their corporate credentials. Iteratively supports Single Sign-On (SSO) federation with:
- Google Apps
- OpenID Connect
- SAML (coming soon)
To configure Single Sign-On (SSO) for your Iteratively account, please reach out to us at [email protected].
No additional configuration is needed to enable Single Sign-On with Google. Simply click the "Log in with Google" button on the Login page, or "Join with Google" button when accepting a colleague's invitation to join them in your Iteratively account.
To enable Single Sign-On with an OpenID Connect (OIDC) IdP, the Iteratively support team will require a few pieces of information from your IT team.
- Client ID
- Client Secret
- Issuer URL
For example, if your organization relies on Okta for single sign-on, the following are typical steps needed to establish a trust relationship with Iteratively.
- Create a new application in Okta for Iteratively. In the Create a New Application Integration dialog, set Platform to Web and Sign on method to OpenID Connect.
- On the Create OpenID Connect Integration page, under General Settings, name your application. And under Configure OpenID Connect, set Login redirect URIs to https://id.iterative.ly/oauth2/idpresponse.
- On the OpenID Connect Client page, under General Settings, confirm that Authorization Code is checked.
- On the same page, under Client Credentials, copy the Client ID and Client secret values. These are the values you'll share with the Iteratively support team.
- On the same page, on the Sign On tab and in the OpenID Connect ID Token section, copy the Issuer URL. This is the last piece of information you'll need.
Note: users must be assigned to your newly created Okta application before they can authenticate to Iteratively. Make sure all users who require access to Iteratively have been assigned.