Okta

Sign in to Xoxoday with
Okta single sign-on

Let employees reach recognition and rewards with the Okta identity they already use.

Book a demo

Get a personalised walkthrough. We respond within one business day.

What you can do

Four things you get once Okta is connected

Okta handles identity. Xoxoday relies on it, so access to rewards follows the controls your IT team already runs.

One login, no new passwords

Sign in with the Okta identity people already have
Employees reach Xoxoday through Okta over SAML 2.0. No separate Xoxoday credentials to create, remember, or reset.
Redirected to Okta to authenticate
Xoxoday sends the sign-in request to Okta, so your Okta authentication policies stay in charge of who gets in.

Access controlled in Okta

Assign users and groups in Okta
Your Okta admin decides which users and groups can use the Xoxoday app, using the same console they already manage.
Centralized authentication
Identity decisions stay with your IT and security team instead of being split across another tool.

Matched to the right profile

Name ID by email or employee ID
The Name ID value can be email or employee ID. It needs to match the user records in Xoxoday so each person lands on their own profile.
Metadata exchange, not manual wiring
Xoxoday provides its service provider metadata and you upload Okta identity provider metadata XML back. Configuration values are copied, not reinvented.

Roll out at your pace

Test before anyone depends on it
Test the connection from the Xoxoday admin interface before changing how employees sign in.
Make Okta the default when ready
Once the test passes, you can optionally set Okta as the default login method.

Use cases

Who runs it, and what for

Three ways teams use Okta with Xoxoday.

IT and Security

Keep authentication in one place

Okta remains the system that decides who is authenticated. Xoxoday relies on it over SAML 2.0 rather than holding its own passwords for your workforce.

People Ops

Reach recognition and rewards without friction

Employees open Xoxoday with the Okta identity they use every day, so recognition and reward programs are one sign-in away.

Admins

Pilot with a group, then go default

Assign a set of users or groups in Okta, test the connection, and set Okta as the default login method when you are satisfied.

How it works

From Okta app to employee sign-in

Step 1

Get Xoxoday service provider details

From the Xoxoday admin interface, copy the SP metadata: ACS URL, Entity ID, and Name ID format.

Step 2

Create the app in Okta

In the Okta Admin Console, create the Xoxoday app with SAML 2.0 and enter the Xoxoday values. Assign users and groups.

Step 3

Upload Okta metadata

Download the Okta identity provider metadata XML and upload it to Xoxoday.

Step 4

Test, then go live

Test the connection from Xoxoday. When it works, optionally set Okta as the default login method.

Setup

SAML 2.0 setup, step by step

Exchange metadata between Okta and Xoxoday, test the connection, and switch over when ready.

Integration type

Native Okta SSO over SAML 2.0, available across Empuls, Plum, and Loyalife.

Sign-in flow

Service provider initiated. Xoxoday redirects the user to Okta to authenticate.

Key settings

Single sign-on URL (Xoxoday ACS URL), Audience URI (Entity ID), and Name ID format EmailAddress.

Prerequisites

Admin access to the Okta Admin Console, Super Admin access to Xoxoday, and your Xoxoday tenant URL.

Learn how to set up
Common Questions

Frequently asked questions

Common questions from IT, security, and HR admins evaluating Okta SSO for Xoxoday.

Still have a question? Talk to us
SAML 2.0.
Service provider initiated. The user opens Xoxoday and is redirected to Okta to authenticate.
Through the Name ID. The Name ID format is EmailAddress, and the value can be email or employee ID. It must match the user records in Xoxoday.
Admin access to the Okta Admin Console, Super Admin access to Xoxoday, and your Xoxoday tenant URL.
Yes. Test the connection from the Xoxoday interface first, then optionally set Okta as the default login method.
Empuls, Plum, and Loyalife are listed for this integration. The step-by-step guide in the help center covers Empuls.

See it in your own Okta setup

A 30-minute call. We'll walk through the SAML 2.0 setup and how rollout to your teams would work.

Book a demo