PICSURE 2.0 Installation

For system administrators installing, configuring and maintaining PICSURE-2.0 instances.

Environment Variables

• PIC_SURE_CLIENT_SECRET
• PIC_SURE_USER_ID_CLAIM
• RS urls for each resource, i.e. IRCT_RS_URL
• some resources may require target URLs, i.e. TARGET_I2B2_URL
• PICSURE_2_TOKEN
• PICSURE2_DB_CONNECTION_USER
• PICSURE2_MYSQLPASS
• VERIFY_USER_METHOD
• TOKEN_INTROSPECTION_URL
• TOKEN_INTROSPECTION_TOKEN

Installing a Resource

Each resource needs to include the following data:

• name
• targetURL - the URL of the resource the ResourceRS will communicate with
• resourceRSPath - the path through PICSURE-2.0
• description - should include instructions on how to include resource credentials
• token - a PICSURE-2.0 token for the resourceRS to communicate with internal PICSURE-2.0 This can be done using the endpoint {PICSURE_URL}/resource. For example, to install an IRCT instance that refers to nhanes.hms.harvard.edu, send a POST with the following body:

[
       {
		"name":"IRCT Resource RS",
		"description":IRCT Resource RS.  For resourceCredentials, please include a token with key 'IRCT_BEARER_TOKEN'",
		"resourceRSPath":"{PICSURE_URL}/v1.4",		
"token":"123ddddd.2399f0....",
                "targetURL" : "https:/nhanes.hms.harvard.edu"
	}
]

Notice that the body is an array of objects, so that multiple resources can be installed at once.