External OAUTH and LTI Developer Key
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2022
11:20 AM
I have a few questions with logging in
- I have an LTI developer key. This works for launches of our tool from Canvas. However, if a user goes to our webpage first, I would like to allow them to login using Canvas as an identity provider.
- With the non-LTI developer key I have this working. Can I use my LTI developer key for this purpose as well?
- Using the LTI key gives me an error with "invalid_scope"
- Can I use the OIDC 3rd party launch mechanism to manage the login instead of using the authorization "code" flow I was using above?
- It would be great if I could use the LTI stuff and public / private keys to manage the logins
- User would go to our app and "Login with Canvas"
- This would start a OIDC flow and bring up the canvas login page
- Once successfully logged in, it would call the redirect_uri as normal
- It would be great if I could use the LTI stuff and public / private keys to manage the logins
Thanks!
Solved! Go to Solution.
1 Solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-09-2022
12:55 PM
I went ahead an deleted and re-added my app. I think to add and LTI application, you need to use the method of installing the app using either the client_id or the LTI URL. (Because of all the other configuration parameters necessary.) If I am incorrect in my assumption here, please feel free to call me out!
Thanks again,
Mark