Skip to content

Commit

Permalink
chore: using partners, alerts, uptime, role
Browse files Browse the repository at this point in the history
zorin edits based on ticket 1302,1204,1306,1307v2
  • Loading branch information
zsamji committed Dec 18, 2023
1 parent 59baf02 commit 5f16840
Show file tree
Hide file tree
Showing 4 changed files with 9 additions and 8 deletions.
2 changes: 1 addition & 1 deletion wiki/Alerts-and-Us.md
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ We have a healthy relationship with our Access Directory Management Services (AD

## Do you think our service (keycloak) is down?

Here are the things to check:
Here are the things to check:

1. Check our uptime status at https://status.loginproxy.gov.bc.ca
2. if you see the IDIR/siteminder uptime alert in red, there may be a larger goverment wide issue. We will provide live updates as we learn more in our [rocketchat channel](https://chat.developer.gov.bc.ca/channel/sso)
Expand Down
2 changes: 1 addition & 1 deletion wiki/Our Partners: the Identity Providers.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@

## Our Partners
## Our Partners
We provide our service with the support of our Identity Provider Partners. An "Identity Provider" is the holder of the identity that is used to log in with. Learn more about our partners and relevant identity provider information.

Your technical team may need to know the identity provider attributes provided, [please visit here to learn more on what we get from our Identity Partners](https://github.com/bcgov/sso-keycloak/wiki/Identity-Provider-Attribute-Mapping)
Expand Down
6 changes: 3 additions & 3 deletions wiki/Using-Your-SSO-Client.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ You can get started by making a request in our Common Hosted Single Sign On appl

1. The names of your product owner and technical contact
2. Someone on your team who knows about OpenID connect. You can learn here too [OIDC Explained by Pathfinder SSO](https://www.youtube.com/playlist?list=PL9CV_8JBQHirMRjBk62jeYUE_MpE4unU8)
3. rough idea on the identity provider (IDIR or BCeID) that you want to use. Learn more here [Our Partners](https://github.com/bcgov/sso-keycloak/wiki/Our-Partners-and-Useful-Information#what-are-identity-providers)
3. rough idea on the identity provider (IDIR or BCeID) that you want to use. Learn more here [Our Partners](Our-Partners:-the-Identity-Providers#what-are-identity-providers)
4. There are some parts of the request where you may need to work with your developer/technical contact:

a. Which usecase/scenario do you need a request for?
Expand All @@ -16,9 +16,9 @@ You can get started by making a request in our Common Hosted Single Sign On appl
6. When the request is complete, you can log in to access your installation json file. Your developer/technical contact will take the details in this file and make use of the details within your application code.

a. [GitHub - bcgov/keycloak-example-apps: Example applications for integrating with keycloak ](https://github.com/bcgov/keycloak-example-apps/tree/dev)
b. You can use roles to enable access to specific pages or data to only those users who connect, with efficiency, data security and simplicity under consideration. [Learn more](https://github.com/bcgov/sso-keycloak/wiki/Creating-a-Role)
b. You can use roles to enable access to specific pages or data to only those users who connect, with efficiency, data security and simplicity under consideration. [Learn more](Creating-a-Role)
c. TLDR: here’s the [video](https://user-images.githubusercontent.com/56739669/231529538-0e1efa5a-51df-401a-99c2-dbc964e8cac6.mp4)

7. Here is a link to our [developer/technical documentation](https://bcgov.github.io/sso-docs/)


Expand Down
7 changes: 4 additions & 3 deletions wiki/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,8 @@ Here’s some reasons as to why this might work for your digital product:

- **Easy setup.** We've made this the #1 feature of this service. You can get your DEV, TEST, and PROD instances running against most of the available identity providers right away. The Pathfinder SSO service already has integrations to the following identity providers:
- IDIR (BC Common Logon Page)
- [Learn about Azure IDIR ](Our-Partners-and-Useful-Information#azure-idir-and-idir)

- [Learn about Azure IDIR ](Our-Partners:the-Identity-Providers#azure-idir-and-idir)
- BCeID Basic (BC Common Logon Page) -- Allows login only with BCeID _Basic_
- BCeID Business (BC Common Logon Page) -- Allows login only with BCeID _Business_
- BCeID Basic & Business(BC Common Logon Page) -- Allows login with BCeID _Basic_ or BCeID _Business_
Expand All @@ -43,12 +44,12 @@ It is technically possible to integrate directly with the various identity provi

- **High Volume Expectations.** The service is shared by many dozens of applications. If one application starts sending millions of login requests, the service itself can experience service degradation which is felt by all the users of all the applications. Pathfinder SSO is managed on the OpenShift Platform and scales fluidly, but there are limits to the resources it can consume.
- **Unique Configuration Needs.** New customers no longer receive a dedicated realm where they can experiment and invent on top of the platform (see "What's Changed" below).
- **BC Services Card Integration Requirements.** Because of the high-security nature of the BC Services Card identity and the private information that is available in the context of a login, BCSC is not allowed to be shared between applications. In a dedicated realm the BCSC integration, once approved and configured by IDIM, can be set up. Since we are not offering dedicated realms at this time, teams that need to integrate with BCSC will need to find another solution (see [BC Services Card Integration](Our-Partners-and-Useful-Information#bc-service-card-integration) for useful advice).
- **BC Services Card Integration Requirements.** Because of the high-security nature of the BC Services Card identity and the private information that is available in the context of a login, BCSC is not allowed to be shared between applications. In a dedicated realm the BCSC integration, once approved and configured by IDIM, can be set up. Since we are not offering dedicated realms at this time, teams that need to integrate with BCSC will need to find another solution (see [BC Services Card Integration](Our-Partners:the-Identity-Providers#bc-service-card-integration) for useful advice).


## Our Partners

We provide our service with the support of our Identity Provider Partners. An "Identity Provider" is the holder of the identity that is used to log in with. [Learn more about our partners and relevant identity provider information](Our-Partners-and-Useful-Information).
We provide our service with the support of our Identity Provider Partners. An "Identity Provider" is the holder of the identity that is used to log in with. [Learn more about our partners and relevant identity provider information](Our-Partners:the-Identity-Providers).

Your technical team may need to know the identity provider attributes provided, please visit here to learn more on what we get from our [Identity Partners](https://github.com/bcgov/sso-keycloak/wiki/Identity-Provider-Attribute-Mapping)

Expand Down

0 comments on commit 5f16840

Please sign in to comment.