Difference between revisions of "2017 Winter Project Week/OAuth2SlicerPathology"

From NAMIC Wiki
Jump to: navigation, search
m
 
(5 intermediate revisions by 2 users not shown)
Line 7: Line 7:
 
==Key Investigators==
 
==Key Investigators==
 
* [http://ebremer.com Erich Bremer] ([https://bmi.stonybrookmedicine.edu Stony Brook Medicine])
 
* [http://ebremer.com Erich Bremer] ([https://bmi.stonybrookmedicine.edu Stony Brook Medicine])
 +
*Steve Pieper, Isomics
  
 
==Project Description==
 
==Project Description==
Line 16: Line 17:
 
|
 
|
 
<!-- Objective bullet points -->
 
<!-- Objective bullet points -->
* Enable OAuth 2.0 authentication within SlicerPathology for purposes of authenticating with various web resources.
+
* Enable [https://oauth.net/2/ OAuth 2.0] authentication within [https://github.com/SBU-BMI/SlicerPathology SlicerPathology] for purposes of authenticating with various web resources.
  
 
|
 
|
 
<!-- Approach and Plan bullet points -->
 
<!-- Approach and Plan bullet points -->
* Direct OAuth 2.0 authentication using python
+
* Direct [https://oauth.net/2/ OAuth 2.0] authentication using python
 
** Identify any needed support libraries that are compatible with 3D Slicer license.
 
** Identify any needed support libraries that are compatible with 3D Slicer license.
* Also checking extending SlicerPathology's use of WebKit to achieve OAuth 2.0 authentication
+
* Also checking to extend SlicerPathology's use of WebKit to achieve OAuth 2.0 authentication.
 
|
 
|
 
<!-- Progress and Next steps bullet points (fill out at the end of project week -->
 
<!-- Progress and Next steps bullet points (fill out at the end of project week -->
*
+
Report from Erich:
 +
 
 +
Hi Steve,
 +
 
 +
I was able to compile a demo browser using the new WebKit in QT 5.7.  Good news, everything works on our Quip site using this browser, from the OAuth 2 authentication process to the OpenSeaDragon viewer to all of the React-generated web screens!  Now, to which gods do I pray, to get QT5.7 into 3D Slicer? :D  QT 5.7 would make for a very exciting addition to 3D Slicer.  - Erich
 +
 
 
|}
 
|}
  
 
==Background and References==
 
==Background and References==
 
<!-- Use this space for information that may help people better understand your project, like links to papers, source code, or data -->
 
<!-- Use this space for information that may help people better understand your project, like links to papers, source code, or data -->

Latest revision as of 16:22, 13 January 2017

Home < 2017 Winter Project Week < OAuth2SlicerPathology

Key Investigators

Project Description

Objective Approach and Plan Progress and Next Steps
  • Direct OAuth 2.0 authentication using python
    • Identify any needed support libraries that are compatible with 3D Slicer license.
  • Also checking to extend SlicerPathology's use of WebKit to achieve OAuth 2.0 authentication.

Report from Erich:

Hi Steve,

I was able to compile a demo browser using the new WebKit in QT 5.7. Good news, everything works on our Quip site using this browser, from the OAuth 2 authentication process to the OpenSeaDragon viewer to all of the React-generated web screens! Now, to which gods do I pray, to get QT5.7 into 3D Slicer? :D QT 5.7 would make for a very exciting addition to 3D Slicer. - Erich

Background and References