Kinescope single sign-on

Team members sign in to Kinescope with your corporate identity provider, and their Kinescope roles come from it too. The setup guides cover Keycloak and AD FS.

Start for free
Setup guide

They left Vimeo, Kaltura and Mux

Every number is what they saved against the platform they left.

All customer stories

Connect your identity provider

Kinescope needs the client ID, the client secret and the provider URL. The redirect URI is the same for every provider.
Keycloak

1. Create a client with Standard flow and Client authentication turned on.
2. Add https://app.kinescope.io/api/oauth2/callback/sso to Valid redirect URLs.
3. Create the Kinescope client roles, link them to your roles in Associated roles, and give Kinescope the client ID, the client secret and the provider URL.
AD FS

1. Create an Application Group with a Server Application that uses the same redirect URI.
2. Generate a shared secret, add a Web API with the client identifier and permit the openid, profile, email, allatclaims and aza scopes.
3. Add issuance transform rules that map LDAP attributes and roles to the Kinescope roles.
Keycloak client settings: Client authentication and Standard flow are turned on, the Kinescope redirect URI is added
AD FS Issuance Transform Rules: rules mapping Course editors, Teachers and Managers to Kinescope roles appear one by one
Keycloak

1. Create a client with Standard flow and Client authentication turned on.
2. Add https://app.kinescope.io/api/oauth2/callback/sso to Valid redirect URLs.
3. Create the Kinescope client roles, link them to your roles in Associated roles, and give Kinescope the client ID, the client secret and the provider URL.

Keycloak client settings: Client authentication and Standard flow are turned on, the Kinescope redirect URI is added
AD FS

1. Create an Application Group with a Server Application that uses the same redirect URI.
2. Generate a shared secret, add a Web API with the client identifier and permit the openid, profile, email, allatclaims and aza scopes.
3. Add issuance transform rules that map LDAP attributes and roles to the Kinescope roles.

AD FS Issuance Transform Rules: rules mapping Course editors, Teachers and Managers to Kinescope roles appear one by one

What single sign-on gives your team

One corporate login

Team members get into Kinescope with the same username and password they use for other work services.

Kinescope Sign in screen: Single sign-on (SSO) is pressed and the Access granted! window appears

Roles from your directory

Six Kinescope roles, from admin to viewer, are mapped from your identity provider, so access follows your company structure.

Kinescope team members: Ben Carter appears in the list right away with the Editor role

Put Kinescope behind your company login

Single sign-on is part of the Mega plan. Book a demo and we will walk your admins through the setup.

Book a demo
See plans

FAQ

Can’t find the answer you need? Check out our Setup guide.

The setup guides cover Keycloak and AD FS. Kinescope needs the client ID, the client secret and the provider URL, and uses the redirect URI https://app.kinescope.io/api/oauth2/callback/sso.

From your identity provider. Create the client roles kinescope-admin, kinescope-editor_plus, kinescope-editor, kinescope-manager, kinescope-accountant or kinescope-viewer and link them to your roles: people get the matching role in Kinescope when they sign in.

The Mega plan.

No, this sign-in is for your team. For viewers, access to a video can go through your own login: Kinescope passes the viewer’s identifier to your server and your rules decide whether the video loads. See private video hosting.

Bring Kinescope under your company login.

Free to start, then from €10/month. No credit card required.

Start for free
All integrations
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.