panda_pal 5.3.6.beta1 → 5.3.6.beta2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 89cb05a4553807543825da2a80fa692689cbbc594a1ed7d7087aaf91b4967039
-  data.tar.gz: 0603fbf7137c94639f1c43252e2ddb5510d8d620a72042587840fed8b18b3d08
+  metadata.gz: 1797969aa547664019c9091a2286fc7ed2958e749c392094db1818e3f2826984
+  data.tar.gz: 53049f9345f939d99f7083dbf49cd3a96f15f3282252a1b4a518aa16d589632d
 SHA512:
-  metadata.gz: c0b5747018b1a1f0fcb6193038e26905a54f4afcc9f4e698954f2ac9924082826d1ed29be76740c4ea389a2c2ccbb3d4d3d303bd0d18b3d4ba6709f7ad79b625
-  data.tar.gz: 0deda4bedafe6583167610e83a86b8d13bd4256094df6158971811c097c3a085345ea18ecaaedcf84cc9b0d890ca6ebf8ee6685ee6e70ada9b71370d4b4c9834
+  metadata.gz: 5088fcf2d122b23da5a2f82ac3054d64fe6974c6c984d9c3726db910bb101b67816b92b8a4b43b47e818fbb85f3bd02a9487d0ca2fd322daeea7cc475bf67b41
+  data.tar.gz: 16d8ee8931f7911a00486f7c5fe0774a4cc80bc942b3477458df0e3bcb0dcc274f519789f10fb1b6e6c4d28419ef45649460c2c09104b95b81cf96c6478fe1bc

data/README.md

@@ -21,6 +21,13 @@ PandaPal::stage_navigation(:account_navigation, {
 
 Configuration data for an installation can be set by creating a `PandaPal::Organization` record.  Due to the nature of the data segregation, once created, the name of the organization should not be changed (and will raise a validation error).
 
+### LTI 1.3 Configuration
+LTI 1.3 has some additional configuration steps required to setup an LTI:
+
+1. If you're running Canvas locally, make sure the `config/redis.yml` and `config/dynamic_settings.yml` files exist in Canvas.
+2. In prod, you'll need to generate a RSA Private Key for the LTI to use. You can set the `LTI_PRIVATE_KEY` ENV variable, or manually set `PandaPal.lti_private_key = OpenSSL::PKey::RSA.new(key)`.
+3. Your PandaPal::Organization's `key` should be `CLIENT_ID/DEPLOYMENT_ID` (which can be found in Canvas). If a Deployment ID is not given, the key should just be `CLIENT_ID/`.
+
 ### Launch URL property
 LTI Spec: `The launch_url contains the URL to which the LTI Launch is to be sent.   The secure_launch_url is the URL to use if secure http is required.  One of either the launch_url or the secure_launch_url must be specified.`
 

data/lib/panda_pal/helpers/controller_helper.rb

@@ -127,7 +127,8 @@ module PandaPal::Helpers
 
     def organization_key
       org_key ||= params[:oauth_consumer_key]
-      org_key ||= "#{params[:client_id]}/#{params[:deployment_id]}" if params[:client_id].present?
+      org_key ||= "#{params[:client_id]}/#{params[:deployment_id]}" if params[:client_id].present? && params[:deployment_id].present?
+      org_key ||= params[:client_id] if params[:client_id].present?
       org_key ||= session[:organization_key]
       org_key
     end

data/lib/panda_pal/version.rb

@@ -1,3 +1,3 @@
 module PandaPal
-  VERSION = "5.3.6.beta1"
+  VERSION = "5.3.6.beta2"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: panda_pal
 version: !ruby/object:Gem::Version
-  version: 5.3.6.beta1
+  version: 5.3.6.beta2
 platform: ruby
 authors:
 - Instructure ProServe
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2020-12-16 00:00:00.000000000 Z
+date: 2020-12-18 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rails