This article is a supplement to our main article on SSO (please read that first for context).
Skedda has a published/official integration with Okta. You can find Okta's detailed guide for the Skedda integration here. Use the Okta guide as your main reference while you're working through the screenshots and process below!
Step 1: 'Browse App Catalog' for the Skedda app
From your 'Applications' settings page in your Okta admin console, select 'Browse App Catalog', as shown in the screenshot above.
From there, search for 'Skedda' in the search bar and select the 'Skedda - SAML' option, as shown in the screenshot below:
Step 2: Add Skedda as an app
Add Skedda as an app, as shown in the screenshot above.
Name the app 'Skedda' in the 'Application label' field, as shown in the screenshot below.
In Skedda, go toSettings → SSO / SAML 2.0.
On the right-hand side, find the Relay State value
Copy only the numeric portion and paste this number into the Venue ID field in Okta.
Click 'Done' to proceed to the next page.
Step 3: Configure 'Relay State' value in Okta
Click on the 'Edit' button under the 'Sign On' section of the Skedda app, in Okta.
Next, copy the 'Relay State' full value from within your Skedda SSO settings page, and paste it into the 'Default Relay State' field in your 'Sign On' settings:
Click 'Save' to complete this step.
Step 4: Provide Skedda with your relevant IdP details
Click on "More details" on the bottom of SAML 2.0 section:
Copy the different values and paste them into their respective fields in Skedda:
The table below shows where you should paste each value from Okta, into Skedda.
Step 5 (Optional): Set up any additional custom attributes as required
If you wish to create attribute rules on the Skedda side for deciding which Skedda user tags are granted to one of your users when they are automatically provisioned during their first Skedda SSO login (as discussed in our main SSO support doc), you might need to pass additional information in the form of custom attributes from Okta to Skedda (i.e. additional custom attributes). For example, you might need to tell Okta to send 'Department' information of a user to Skedda. To do this, click the "Edit" option under the "Sign On" tab of the Skedda application in Okta...
... and then click the small "expand" arrow next to "Attributes (Optional)":
This will then allow you to add further attributes as you require, using the Okta editor:
Step 6: Setup Complete!
Finally, review the "Assignments" page for the Skedda app in Okta. From here, you'll be able to make sure that the appropriate users/groups are assigned access to the SSO integration between Skedda and Okta, in your organization.
Once that’s completed, you’re all set to begin testing!
Supported SSO Features
Skedda supports industry-standard SAML 2.0 authentication and provides the following Single Sign-On (SSO) flows:
IdP-initiated SSO
Users start the login from Okta. When a user clicks the Skedda application tile in Okta, Okta sends a SAML response to Skedda, and the user is signed in.
SP-initiated SSO
The sign-in process is initiated from Skedda tenant.
From your browser, navigate to Skedda sign-in page.
Click on "Log in with SSO"
Enter your email. You will be redirected to the Okta sign in page.
Enter your Okta credentials. You will be redirected to Skedda and be logged into the venue.
Both login flows are fully supported and can be used interchangeably.
SAML Attributes
Required attributes
Skedda requires the following user attributes to be included in the SAML assertion in order to authenticate users successfully:
Attribute | Description |
Required. Used as the user’s unique identifier during SSO. | |
FirstName | Required. Used to populate the user’s display name. |
LastName | Required. Used to populate the user’s display name. |
These attributes correspond to the “Expected user attributes” shown in the Skedda SSO configuration panel.
Optional SAML Attributes
Skedda does not define a fixed list of optional SAML attributes. However, administrators may optionally include custom SAML attributes in the SAML assertion if they wish to use them with Skedda Attribute Rules, for example to assign user tags based on IdP-provided values.
Example custom attribute usage:
Attribute | Description |
Department | Optional. Can be mapped to a Skedda user tag using Attribute Rules. |
Custom attributes are entirely optional and not required for SSO authentication.
Walkthrough video
If you’d like to set your SSO integration while following along with a video walkthrough, take a look at the video below to get going!
If you're having trouble getting SSO to work after setting it up, take a look at our SSO Troubleshooting article!
Please also feel free to reach out to our support team if you have any questions or issues in the setup process.