Single Sign On (SSO) for Evolution Gaming

Evolution Gaming develops, produces, markets and licenses fully-integrated B2B Live Casino solutions to gaming operators. The company was founded in 2006 and is a leading provider of Live Casino solutions.

Here we are going to look at two scenarios where Evolution Gaming came up with new requirements and how miniOrange solutions helped them. In one use case, they wanted to manage the Jira server license limit and in the other one, they needed a way to handle both internally and externally stored users for Jira and Confluence. These scenarios and their solutions are discussed in brief below.

Use case 1: User Provisioning and Deprovisioning 

Being an online gaming company, the user registrations rate in Evolution Gaming is very high. As a result, their user count threshold for the Jira and Confluence license is reached frequently. They store and manage their users in Okta. In order to manage the user limit, they needed auto-activation and deactivation feature which activates and deactivates a user in Jira and Confluence servers whenever the operation is performed in Okta.

Solution provided by miniOrange: 

miniOrange has provided a solution that automatically activates/deactivates a user in both Jira and Confluence when the user is activated/deactivated in Okta. miniOrange has achieved this by introducing an Okta API based user provisioning solution for Atlassian applications (Jira and Confluence) using existing SSO plugins. Here, the Atlassian application sends an authenticated request to Okta to fetch the user information and based on the response received, the user information is updated in Jira and Confluence.

The request for user information is sent regularly after a certain time interval. This means that the changes in Okta will be regularly updated in both Jira and Confluence. So Jira or Confluence administrators don’t need to manually update the users now.

For example, if a user Adam is deactivated in Okta then Adam’s account will get deactivated in both Jira and Confluence automatically and Atlassian admins don’t need to manually deactivate Adam’s account in each of the applications.

Along with this miniOrange provides Just In Time user provisioning, where users’ information is also updated on each login.

 

Evolution Gaming success story -user sync

Use case 2: Log in with Internal and External users

Evolution gaming has multiple customer portals for users to raise support tickets in Jira Service Desk. But users cannot be managed in the same way for all the customer portals. This is because all the users are not managed in one place, some of them are managed in the Identity Provider i.e. OKTA whereas others in Jira’s internal directory. So they were looking for a product that can differentiate between internal and external users and take users to the appropriate login pages.

Solution provided by miniOrange: Customer Portal Based Redirection for Internal and External user login

So, miniOrange provided a solution of redirection based on the customer portal. This solution differentiates the internal and external users based on the Customer Portal URL accessed as the users accessing a particular portal were stored in either Okta or internally in Jira. The admin can decide log in through Okta or log in through Jira using the ‘Auto Redirect to IDP’ and ‘Disable Auto Redirect to IDP’ for selective portals features.

Let us consider, for example, the Jira administrator has enabled the ‘Auto Redirect to IDP’ option and configured Portal 1 in the ‘Disable Auto Redirect to IDP’ option in the plugin. Thus the users accessing the Portal 1 are considered as internal users and are prompted to log in with the Jira login page and users accessing any other Portal are considered as external users and are redirected to Okta login page for SSO. (Refer to the diagram below)

This way all portals can be customised to show any Identity Provider’s login page or Jira login page.

 

Benefits of using miniOrange SSO solution:

  1. Ease of Managing Users: User operations have to be performed only in the Identity Provider for the changes to be carried over to the service provider. So the administrator does not need to manage users in multiple places.
  2. Easy to Control user limit: Using this solution, it is easy to manage the user limit for the service provider license.
  3. Saves admin’s time: This solution saves the administrator’s time in managing users allowing them to focus their time on something else.
  4. Ease of handling both internal and external users: With the help of solutions provided above, both internal and external users are redirected to respective login pages (the Jira login page and the IDP login page).
  5. Cost-effective: As this solution manages the user limit for the service provider license, there is no need to buy a higher user tier license.
  6. Ease of Access: For the end-users, it reduces the responsibility of managing multiple sets of usernames and passwords.

 

Resources:

Follow the link to learn how to Setup miniOrange User and Group Sync App for Jira with Okta.

Follow the link to learn how to Setup miniOrange User and Group Sync App for Confluence with Okta.

Follow the link to learn how to Setup SAML SSO between Okta and Jira.

Follow the link to learn how to Setup SAML SSO between Okta and Confluence.

Contact Us:

If you don’t find what you are looking for, please contact us at info@xecurify.com or call us at +91 978 658 9387 to find an answer to your question about Single Sign-On (SSO). You can also reach out to us from our ServiceDesk portal.