DSA_OAuth_changesIn digital_slide_archive/devops/dsa/provision.yaml, set the following:`` pip: - girder-oauth==3.2.3.dev12 rebuild-client: True `File Girder Container File Pathuser.py => /opt/girder/girder/api/v1/user.pyApp.js => /opt/girder/girder/web_client/src/views/App.jsrest.js => /opt/girder/girder/web_client/src/rest.jsExplanation of Changes: user.py: Changed the getMe() function to redirect to OAuth Sign-In link if user is not already signed in - This would need to change for general Girder implementations, but for our use case where we want the…
Source code on GitHub.
In digital_slide_archive/devops/dsa/provision.yaml, set the following:
``
pip:
- girder-oauth==3.2.3.dev12
rebuild-client: True
`
File Girder Container File Path
user.py => /opt/girder/girder/api/v1/user.py
App.js => /opt/girder/girder/web_client/src/views/App.js
rest.js => /opt/girder/girder/web_client/src/rest.js
Explanation of Changes:
user.py: App.js
Changed the getMe() function to redirect to OAuth Sign-In link if user is not already signed in
- This would need to change for general Girder implementations, but for our use case where we
want the user to always be logged in with their credentials, this works.n
Added a default First and Last name value to the user in the case that it is null.
- For OAuth it seems that some users (particularly external users in the org) can have no set
first or last name, which causes Girder to break. This was addressed by adding default values
for those fields.
:rest.js`:
Added handling for the redirect in user.py to circumvent CORS issues.
- This would need to be adjusted for any changes to the edited behavior in user.py.
Added handling to set girderToken cookie if it is not set but the girderToken is
- Girder OAuth checks for the girderToken cookie, but that cookie is not set when signing in
with OAuth. This breaks lots of endpoints that check for the cookie to authenticate,
including EventStream routes.