Pics.io users have the ability to configure a default Identity Provider to force Single Sign On (SSO). This article explains how to configure Okta as the Identity Provider to facilitate SSO with the Pics.io application.
Prerequisites
In order to proceed with configuring login with SSO through Okta, you must:
Be an administrator of Okta tenant
Have a Pics.io account with permission to manage Okta integration
Have an active Okta Single Sign-on Integration (Available on the Enterprise Plan)
Configuration steps
As an Okta tenant administrator, you will create the Pics.io integration and obtain some information that you will later have to save in the Pics.io settings.
Step 1. Add the Pics.io App to Okta
Log in to your organization’s Okta tenant as an administrator.
Navigate to Applications > Applications and then click Create App Integration.
Select Sign-in method OIDC - OpenID Connect and Application Type Web Application, click Next.
Give it a meaningful App integration name. This is the name under which the Pics.io app will appear in users' Okta dashboard.
Select the Grant Type Authorization Code.
Add the Sign-in redirect URL https://pics.io/auth/okta/callback
Assign the app integration to users in the Assignments section.
Click Save.
Step 2. Configure SSO in Pics.io
Navigate to Applications > Applications and select newly created integration. Find your Okta Domain (or Issuer URL). It appears in a popup when clicking a username in a top toolbar.
Note: If the Okta domain is not found, copy the URL you use to access your Okta tenant from the browser address bar. It looks like https://acme-admin.okta.com/admin/apps/active. Be sure to remove everything appearing after okta.com and remove the "-admin" suffix and "https://" prefix. As a result, it should look like acme.okta.com. This is your Okta Domain.
Under the General tab of the Pics.io application, copy the Client ID and one of Client Secret.
In Pics.io, fill this in under the Okta domain, Okta Client ID, and Client Secret fields. After that Okta users may use this link to initiate the SSO login process by navigating it directly from the browser. It is also possible to add this link to end users' dashboards.
Note: These values allow Pics.io to communicate with Okta. The Client ID is a public identifier for the client that is required for all OIDC flows. The Client Secret is a private identifier that you should not share or broadly distribute.
Step 3. Assign users. It's optional.
Before leaving Okta, ensure you have given yourself and any other target users access to the Pics.io application. You can do this by going to Applications > Pics.io > Assign and then assigning to either the target people or group.
Click the Assignments tab under the configured Pics.io app, then click Assign. Leveraging Groups is recommended to assign access. If assigning access to People, ensure the User Name is a valid email.
Assigned users via group or directly will now be able to log into Pics.io via SSO through the Pics.io website or on their Okta dashboards. Remember that accounts won't be created in Pics.io until the initial SSO login.


