Releases Q&A: 2022-06-08 Accounts Settings Developer Key Account Binding

[HeatherAhern]

Looking to discuss this feature from the 2022-06-08 Deploy Notes? Post a reply and start a conversation!

ADD FEEDBACK FOR THIS FEATURE IN Q&A TOPIC

• This topic is for feature discussion only—Please share use cases, best practices, questions, clarifications, etc. regarding this feature.
• Please thread replies as possible to keep posts organized. This will help everyone to track discussions and to participate.

ADDITIONAL FEEDBACK—WHERE TO POST IDEA SUGGESTIONS AND SUBMIT BUG REPORTS

• Idea requests for the Product Team to consider should be submitted in ideas.canvaslms.com . This is the best way to ask for additional or alternative functionality than what is included in the release. Linking to the related idea here so others can find it is encouraged!
• Bug reports should be submitted to Canvas Support. This way, cases can be connected and uniform updates can be provided to those involved. Bugs will not be triaged in this thread

[leward]

I'm confused.  We've been able to add LTI 1.3 tools to subaccounts in this manner for quite a while.  What has changed?

[audra_agnelly]

I'm also confused about what has changed with this update. In addition to @leward's comment, why is this under the heading "Consortium Updates" in the deploy notes? There's no explanation of what this has to do with consortia in the notes.

[philmac]

What am I missing here?

I followed those same steps in 2020 to add a tool by client ID to a sub-account. 

[tcs1]

Was there a bug here perhaps? We've been deploying with Client IDs to subaccounts for quite some time.

[SarahBlanton]

@HeatherAhern Can someone from Instructure reply here perhaps? I have the same questions as the other folks.

[chriscas]

I notice the release notes make mention of using the same key in *multiple* subaccounts.  I've definitely installed with a root account key into a subaccount before and know it's worked fine.  I don't think i've ever tried installing the same app/key in multiple subaccounts though, so maybe there was something broken in that scenario that's being fixed here.  Regardless, it would be awesome if someone from Instructure could chime in here and clarify what is actually being changed/fixed.

-Chris

[AlexisNast]

Hello!

I'm the Product Manager on our LTI team, and I'd like to help clarify this change. This will only affect instances set up as consortia (where the root account has "Consortium parent account" selected under Settings in the "Canvas Cloud Information." section.) Additionally, this will only affect child accounts which are set as "not a primary settings root account." So far we are only aware of one institution which has this configuration, so I don't believe anyone in this thread will see a difference. The change for those accounts is that the developer keys will not only work for the subaccounts, but will be available without user intervention. We are working toward providing more features for centrally managed consortia which require identical setups in multiple root accounts, and this is the first step toward that goal. My apologies for the lack of clarity, I will work to improve these notes in the future.

Please let me know if you have any further questions!

Alexis

[SarahBlanton]

Thank you!

[audra_agnelly]

As admins, many of us are familiar with the use of consortia in Commons and not as a configuration in an account instance. Thanks for clarifying!