fix: Fix LTI 1.1 template rendering on LTI 1.1 embeds

3.4.3

Merge pull request #233 from open-craft/giovanni/fix-django-template-…

Fix quote rendering on LTI 1.1 form

Fixed quotes being rendered on LTI 1.1 launch templates by switching to Django templates.
Internationalized strings on LTI 1.1 launch page.

Use launch_url for oidc login target_link_uri parameter

The target_link_uri specified within the OIDC login URL parameter is different from the claim message construction target_link_uri. According to documentation, they need to be the same and the value should be the tool launch URL.

Update the code to match the spec above.

v3.4.0

What's Changed

• chore: Post Django32 Cleanup by @edx-requirements-bot in #223
• Fix Version Number by @aht007 in #229

Full Changelog: 3.3.0...v3.4.0

Add support for JWK Keysets for LTI 1.3

3.3.0

Merge pull request #216 from open-craft/felipetrz/BB-5168-upstream-jw…

Dynamic custom parameters support with the help of template parameter processors.

Able to set dynamic custom parameters in the LTI consumer Xblock in Studio so that dynamic value should be resolved/substituted with a value resolved by the processor and added to the launch URL in order to be used by the provider as needed.

In order to make this happen, we must map the dynamic value template with the custom parameter processor in the LTI_CUSTOM_PARAM_TEMPLATES just like mentioned above, the custom parameter processor must be defined in the customer package.

If LTI_CUSTOM_PARAM_TEMPLATES is not defined, the dynamic custom parameters will not affect existing logic.

feat: styling for "new window" modal

Updated styling in the new modal fix for lti in new window modal to match the paragon styling.

What's Changed

• feat: style new window modal by @connorhaugh in #211
• chore: update version by @connorhaugh in #212
  Full Changelog: 3.1.1...3.1.2

feat: Long-term fix for cross-origin iFrames

Our previous LTI Component XBlock provides an option to "View resource in a New Window", which uses JS to launch a new window/tab. These capabilities were removed in Chrome v92. Chrome provided a temporary work-around which we now use in production. But we now need to design and implement a longer term fix. These issues have since migrated to Safari, and “before other browsers implement this change, which they have indicated that they will” we need to resolve this issue with something other than band-aids. Google Chrome’s and Safari’s move, however, is aligned with making iFrame technology more secure, which we can read as a signal that the industry will continue to advance in the direction of iFrames. This fix replaces the browser dialog with a custom javascript one.
#204.

What's Changed

• build: latest pylintrc from edx-lint by @nedbat in #199
• Python Requirements Update by @edx-requirements-bot in #198
• Python Requirements Update by @edx-requirements-bot in #200
• Python Requirements Update by @edx-requirements-bot in #202
• Python Requirements Update by @edx-requirements-bot in #203
• Python Requirements Update by @edx-requirements-bot in #205
• feat: advertise constraints in setup.py by @edx-requirements-bot in #206
• Python Requirements Update by @edx-requirements-bot in #208
• fix: Long-term fix for cross-origin iFrames by @connorhaugh in #204
• Standardize version number placement by @aht007 in #207
• docs: reflect changes in changelog and version by @connorhaugh in #209

New Contributors

• @connorhaugh made their first contribution in #204
• @aht007 made their first contribution in #207

Full Changelog: 3.1.0...3.1.1

Added Django 3.2 support

What's Changed

• feat: Added support for django32 by @Jawayria in #195

Full Changelog: 3.0.4...3.1.0

Replace jsonfield2 with jsonfield

• Switched from jsonfield2 to jsonfield as the earlier one has archived and merged back in the latter one.