The BC Government Single Sign-On (SSO) service, based on the Open Source Keycloak (aka Red Hat SSO) product, provides an industry standard (OIDC) and enterprise-policy compliant means of implementing authentication and authorization within applications that is also simple for development teams to provision, utilize and manage.
Development teams are provisioned a set of
realms within a multi-tenant instance of Keycloak running in the OpenShift Container Platform (OCP) platform that can be self-administered and customized to the needs of one or more applications.
Each realm will be configured with a set of centrally-managed identity providers (such as BCeID, IDIR, and GitHub) based on the needs of the team. Teams may add integrations with other identity providers within their realms based on their needs.
Users of this service gain access to the following:
Development teams are provided with a set of
realms (an isolated configuration/namespace within Keycloak), corresponding to their deployment environments (dev, test, and prod). Realms come configured out-of-the-box with one or more of the following identity providers:
- BC Government IDIR
Each realm has an its own web interface that development teams can use for self-serve administration. To integrate with an application the following industry standard protocols are available:
- OpenID Connect (OIDC)
- SAML 2.0
OIDC is the recommended protocol, and at the time of this writing there are no BC Governement teams using the SAML protocol with Keycloak.
For native mobile apps, the BC Government developer community has produced the following SDKs to provide integration with Keycloak for the purposes of authentication:
There is a vibrant community around the SSO service that can be found on the
#sso channel in the BC Government Pathfinder RocketChat. This is the forum for asking questions and following developments on the service.
This service is offered to BC Government development teams building cloud native web or mobile applications. Teams wishing to use this service should connect with the Enterprise DevOps Team to discuss their needs and ensure alignment prior to making a request.
Teams wishing to have realms created should follow the steps outlined at SSO Realm Request.
If for you need further information, reach out to Todd Wilson, Director of Enterprise DevOps, Office of the Chief Information Officer; he can be located in the corporate directory.
The SSO system is deployed in a high-availability configuration within the highly-available BC Government OpenShift cluster. This service is available 24/7 with best effort to restart failed systems.
Realm provisioning requests will be reviewed and handled during normal business hours.
The best source of help is the vibrant community of development teams using SSO for their projects. You can find this highly talented and knowledgeable group in the
#sso channel on RocketChat.
For help beyond this contact one of the SSO administrators via the
#devops-sos channel on RocketChat.
For you my friend, there is no charge for this service.
The team supporting this service administers the Keycloak application, its supporting database, as well as the
master realm and global identity providers (IDIR, BCeID, and GitHub). When your realm is set up they will assign a member of the requesting development team to be the realm administrator; this person will take care of the day-to-day operation and configuration of the realm.
SSO interfaces with other BC Government services to provide authentication via IDIR or BCeID. These services are managed by different teams from the team providing Keycloask. For these services contact support via the standard
7-7000 support channel.
RocketChat is the primary mode of communication. Specifically the
#sso channel should be used for engage the community for best practices, configuration and troubleshooting questions.
For cluster wide service notifications that may impact SSO monitor the
#devops-alerts channels in RocketChat.
For teams without RocketChat access, escalation, or to talk to a person IRL contact Todd Wilson, Director of Enterprise DevOps, Office of the Chief Information Officer.
This section is not yet completed.
* request workflow(s) * change management * service improvements * service level * security reviews
If you intend to use BCeID you must contact the team that oversee BCeID prior to a production launch. This is required so that your project can get added to the BCeID catalogue and to understand what BCeID authentication options are available and what ones are deprecated.
Copyright 2019 Province of British Columbia This work is licensed under the Creative Commons Attribution 4.0 International License. To view a copy of this license, visit http://creativecommons.org/licenses/by/4.0/.
This document is based heavily on Service Definition Questions and Checklist from UC Santa Cruz.