From 5d6468b0f2f39ff877b9496a777a20c40ea8d9c0 Mon Sep 17 00:00:00 2001 From: jonathan langlois Date: Thu, 23 Nov 2023 15:02:03 -0800 Subject: [PATCH] chore: links update links in new wiki --- wiki/CSS-App-Valid-Redirect-URI-Format.md | 9 --------- ...ogin-Page-and-if-you-ABSOLUTELY-need-it.md | 20 ------------------- wiki/SSO-Onboarding.md | 2 +- wiki/index.md | 2 +- 4 files changed, 2 insertions(+), 31 deletions(-) delete mode 100644 wiki/CSS-App-Valid-Redirect-URI-Format.md delete mode 100644 wiki/Recommend-Skipping-the-Keycloak-Login-Page-and-if-you-ABSOLUTELY-need-it.md diff --git a/wiki/CSS-App-Valid-Redirect-URI-Format.md b/wiki/CSS-App-Valid-Redirect-URI-Format.md deleted file mode 100644 index ccf48f84..00000000 --- a/wiki/CSS-App-Valid-Redirect-URI-Format.md +++ /dev/null @@ -1,9 +0,0 @@ -In CSS app, the allowed URI syntax consists of two parts with `://` in the middle: -- `://` -- `scheme`: the following rules must be met: - 1. must be greater than one character. - 2. must start with an alphabet character followed by optional characters (`alphabets`, `hyphens(-)`, and `periods(.)`) -- `path`: a minimum of one character is required except for `white spaces` and `#`. -- For the `dev` and `test` redirect URIs please refer to the regular expression `/^[a-zA-Z][a-zA-Z-\.]*:\/\/\S+/` -- For `prod` URIs there are additional restrictions on wildcards (*) please refer to the regular expression `/^[a-zA-Z][a-zA-Z-\.]*:\/\/([^*\s]+\/\S*|[^*\s]*[^*\s]$)/`. This prevents domain level wildcards like `https://www.example.com*` while accepting non-domain level wildcards `https://www.example.com/*`. -* We made an exception to allow wildcard (*) in the dev, and test environments to satisfy the various development processes. diff --git a/wiki/Recommend-Skipping-the-Keycloak-Login-Page-and-if-you-ABSOLUTELY-need-it.md b/wiki/Recommend-Skipping-the-Keycloak-Login-Page-and-if-you-ABSOLUTELY-need-it.md deleted file mode 100644 index 606c69ac..00000000 --- a/wiki/Recommend-Skipping-the-Keycloak-Login-Page-and-if-you-ABSOLUTELY-need-it.md +++ /dev/null @@ -1,20 +0,0 @@ -# We recommend to skip the Login Page but if you have a need for it, read on - -As you've read in our guidance in setting up a keycloak client do's and don'ts [here](https://github.com/bcgov/sso-keycloak/wiki/Using-Your-SSO-Client#dos-and-donts), our recommendation is to skip the [keycloak login page](https://github.com/bcgov/sso-keycloak/wiki/Using-Your-SSO-Client#do-skip-the-keycloak-login-page) ie - -**Do Skip the KeyCloak Login Page** -> In KeyCloak, if the realm that contains your client has more than one IDP configured, KeyCloak shows a page that prompts the user to select which IDP they want to log in with. Almost all teams have chosen to hide this page from their users by specifying the IDP as a query string parameter in the KeyCloak Authorization URI value behind their login button. The query string is 'kc_idp_hint'. (The IDPs available will depend on the standard realm in which your client exists.) By specifying the IDP in this way, the user will be redirected directly to the login page for the identity provider and will not see the KeyCloak login choice page at all. - -**Need dedicated text for login page** - -If you are a client of ours and have an **absolute** need to have a dedicated set of text for your login page, through [our app](https://bcgov.github.io/sso-requests), you can specify the text under the field setting **Keycloak Login Page Name** - - -![image](https://user-images.githubusercontent.com/56739669/171695377-60fa5c47-e867-4097-b140-6df8d5155cdd.png) - -#### *Have any questions? We would love to hear from you.* [![Semantic description of image](https://user-images.githubusercontent.com/87393930/133688357-09f82374-ba18-4402-8089-c0a989dde882.png)][2] - - - -[2]: https://chat.developer.gov.bc.ca/channel/sso -[3]: https://[mail](mailto:bcgov.sso@gov.bc.ca)[email](mailto:bcgov.sso@gov.bc.ca) diff --git a/wiki/SSO-Onboarding.md b/wiki/SSO-Onboarding.md index 5cac72ff..03a0918c 100644 --- a/wiki/SSO-Onboarding.md +++ b/wiki/SSO-Onboarding.md @@ -22,7 +22,7 @@ Please visit [BCGov Cloud Services](https://digital.gov.bc.ca/cloud/services/) ## Start Using your OIDC Client Configuration -Once you have your client details, you can configure your application to use the service for your application login. For helpful advice on integration see [Using Your SSO Client](https://github.com/bcgov/sso-keycloak/wiki/Using-Your-SSO-Client) or **if you are eager**, check out our [keycloak example apps](https://github.com/bcgov/keycloak-example-apps) +Once you have your client details, you can configure your application to use the service for your application login. For helpful advice on integration see [Using Your SSO Client](https://bcgov.github.io/sso-docs/category/getting-started) or **if you are eager**, check out our [keycloak example apps](https://github.com/bcgov/keycloak-example-apps) #### *Have any questions? We would love to hear from you.* [![Semantic description of image](https://user-images.githubusercontent.com/87393930/133688357-09f82374-ba18-4402-8089-c0a989dde882.png)][2] [2]: https://chat.developer.gov.bc.ca/channel/sso diff --git a/wiki/index.md b/wiki/index.md index e49b2479..d72c03f5 100644 --- a/wiki/index.md +++ b/wiki/index.md @@ -38,7 +38,7 @@ The Pathfinder SSO service (also known as "KeyCloak" or "RedHat SSO") consists of two offerings: Standard and Custom. -Over the years, we’ve engaged and learned that the majority of our clients can make use of our standard service, so we created the [Common hosted Single Sign on (CSS) App](https://bcgov.github.io/sso-requests/). It’s a simple way for application development teams to set up login functionality for their app from approved [identity providers](https://github.com/bcgov/sso-keycloak/wiki/Useful-References#identity-provider) over a standard and secure protocol aka to help you obtain the technical details for your login component. Learn more about [onboarding with us here](https://github.com/bcgov/sso-keycloak/wiki/SSO-Onboarding). +Over the years, we’ve engaged and learned that the majority of our clients can make use of our standard service, so we created the [Common hosted Single Sign on (CSS) App](https://bcgov.github.io/sso-requests/). It’s a simple way for application development teams to set up login functionality for their app from approved [identity providers](https://github.com/bcgov/sso-keycloak/wiki/Useful-References#identity-provider) over a standard and secure protocol aka to help you obtain the technical details for your login component. Learn more about [onboarding with us here](https://bcgov.github.io/sso-docs/category/getting-started). ## Our Partners