-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gh 963/update openpedigree to use keycloak for authentication #75
Closed
AlgyTaylor
wants to merge
280
commits into
phenotips:master
from
Manchester-Centre-for-Genomic-Medicine:gh-963/update-openpedigree-to-use-keycloak-for-authentication
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ic-Medicine/open-pedigree into mcgm-version
Trying to fix the env vars problem - maybe switching to dev mode will help?
Environmental variables not being passed through `process.env` it seems. console.log'ed the result to see, hardcoded the values in to the JS file to try to get the thing working!
…dicine/open-pedigree into develop
Update the `GetOpenPedigreeData` GraphQL query to fetch the entire family record, rather than just the `open_pedigree_data` fields. This will allow us to extend the functionality to retrieve patient demographics and other details on the related cohort.
Update the `GetOpenPedigreeData` GraphQL query to fetch the entire family record, rather than just the `open_pedigree_data` fields. This will allow us to extend the functionality to retrieve patient demographics and other details on the related cohort.
…gm/update-gwl go-1756: update gql to fetch whole family record
…gm/update-gwl Mcgm/update gwl
Update controller to fire a `pedigree:person:set` event when a field is updated. This allows code to dynamically update the rest of the node based on the data provided, e.g. use a patient identifier to complete the rest of the demographic details.
Update all dependencies using `npm audit fix`, followed by `npm update`.
…-1292/add-set-event-listeners Go 1292/add set event listeners
…-1292/add-set-event-mcgm Go 1292/add set event mcgm
Add an event listener to OpenPedigree to retrieve demographic data when an NHS number is entered, then set the appropriate fields in the pedigree diagram using this data.
…-1732/use-geno-for-demographics go-1774: live import gen-o demographics
… to hpo.jax.org API.
…it-phenotypic-features-with-pedigree Edit phenotypic features with pedigree
…the demographic details.
…o-terms-selectize-js-control Replaced HPO terms selector with selectize.js control linked to hpo.jax.org API.
Update the MCGM-specific query in OpenPedigree to retrieve pedigree data from the appropriate view.
…inked to orpha.net API.
…it-condition-with-pedigree go-1740: replaced disorder terms selector with selectize.js control
…cgm-version Mcgm version
…cgm-version Mcgm version
…lgyTaylor-patch-3 gh-660: add test env for test
Update GraphQL mutation to use the `family.pedigree` table to save data to.
Update OpenPedigree to read the pedigree data from the versioned pedigree data available in the `family.pedigree` table, via the `pedigree` calculated field in Hasura.
…h-689/resync-open-pedigree Gh 689/resync open pedigree
Update the `getDemographicsPDS` function so that it uses a consistent name selection method in relation to the main Gen-o platform. This functions are not directly linked and will require additional work to keep them up-to-date.
…h-721/incorrect-patient-name-displayed-when-creating-new-record gh-721: make spine name lookup consistent
Update text used to change the attribute that pedigrees are shaded by, as there was some comfusion in relation to what the previous wording had meant.
…h-779-change-wording-for-currently-selected-highlighted-attribute Gh-779: change wording for currently selected highlighted attribute
Update the GraphQL query to match the new disorder database structure.
Update app.js to give the `auth0` variable a wider scope.
Update the method used to create a new auth0 client to more closely follow that shown in the auth0 documentation. Remove some unnecessary `console.log` calls.
Remove `window` namespace from `setInterval` method call...
Use `npm install keycloak-js` to install the Keycloak JavaScript client. Run `npm audit fix` to automatically fix some issues with dependencies.
Update webpack to use V5 as this is required for the keycloak-js libray.
AlgyTaylor
deleted the
gh-963/update-openpedigree-to-use-keycloak-for-authentication
branch
October 9, 2024 15:18
AlgyTaylor
restored the
gh-963/update-openpedigree-to-use-keycloak-for-authentication
branch
October 9, 2024 15:22
AlgyTaylor
deleted the
gh-963/update-openpedigree-to-use-keycloak-for-authentication
branch
October 9, 2024 15:22
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.