Issues

Clean up the object model to align with the SMART on FHIR launch specification (see desc)
JCL-50
Release the Java Client with logout functionality
JCL-49
A user of the HSPC Java Client is able to log out and then log in with a different user account (including the auth server session)
JCL-48
A user of the Quick Start Java Spring Standalone MVC For Provider guide runs the guide and sees information from the signed in user
JCL-47
The Java Client Library has an NPE during the standalone launch flow (because they have no launch parameter)
JCL-46
(High priority from Daren!) A user of the Java Client library optionally receives a "null flavor" representation when querying by code
JCL-45
A user of the Java Client Library is able to establish an encounter context for subsequent queries
JCL-42
HSPC Java Client examples not working
JCL-41
A user of the Java Client Library is able to issue queries that are restricted to the SMART app's Patient Context
JCL-40
SMART Launch Support
JCL-39
The Java Client library does not use a connection pool for connections to the auth server
JCL-38
A user of the Java Client library is able to connect to the authentication server when behind a corporate proxy server.
JCL-37
A user of the Java Client library is able to use the HAPI 2.0 and FHIR 1.6 versions
JCL-34
Send authorization credentials (in the header) to API server when requesting a launch context
JCL-31
Pull the Java Client out of the HSPC Reference Impl Repo
JCL-30
A consumer of the Java Client is able to receive a Patient Context (similar to SMART Javascript lib)
JCL-25
Part 2 - An application developer uses JWT to authenticate a backend service to the HSP Sandbox (which style, asymmetric or symmetric, SMART needs to specify)
JCL-18
Why does CodeFlowAuthorizer need a FhirSessionContextHolder?
JCL-2
Expose the entire access token response to clients
JCL-3
Unable to connect to sandbox when behind a proxy server
JCL-1
The Bilirubin application is able to use the latest conformance statement and launch sequence from SMART.
JCL-12
A consumer of the HSPC sandbox is able to receive a conformance statement based on SMART's latest standards (REST server, JS client migration, Java Client)
JCL-8
A consumer of the HSPC sandbox (server and Java client changes) is able to use the lastest SMART launch sequence to authenticate
JCL-5
(Part 2) An application developer is able to create a Backend Service sample app for Java and Spring IOC (code and instructions)
JCL-14
An HSPC engineer publishes the HSPC Java Client library to a public maven repository
JCL-13
1-25 of 44