Skip to content

Commit

Permalink
Merge pull request #127 from OneComputerGuy/main
Browse files Browse the repository at this point in the history
Features:

Added new menu structure
Added docs for AGS
Modified and reworked LTI 1.3 docs
Created and reworked UEF docs
Reworked Proctoring menu structure
Modifications:

Added versioning tracker as default for documents (no need to manually add them again)
Deletions:

Removed author box from the documents
  • Loading branch information
OneComputerGuy authored Oct 11, 2024
2 parents 9f95db1 + e854da3 commit aa7dce8
Show file tree
Hide file tree
Showing 117 changed files with 16,096 additions and 4,606 deletions.
4 changes: 3 additions & 1 deletion .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -20,4 +20,6 @@

npm-debug.log*
yarn-debug.log*
yarn-error.log*
yarn-error.log*

.obsidian
Original file line number Diff line number Diff line change
Expand Up @@ -13,8 +13,7 @@ summary: As browsers continue to lock down cookies, particularly with iframes, t

In testing with the [Google Canary Chrome Browser](https://www.google.com/chrome/canary/), one of our clients discovered an issue that was blocking users from logging in to their Learn instance. After much troubleshooting, we discovered a multi-layer issue that brings us to, you guessed it, [cookies](https://docs.anthology.com/blog/2020/10/15/Cookies-and-Browsers).

> **This affects clients in SaaS with Ultra Base Navigation enabled using Ultra integrations that rely on UEF** <br/>
> **Review UPDATE in LTI 1.3 section. This post previously mentioned a bug that no longer exists.**
> **This affects clients in SaaS with Ultra Base Navigation enabled using Ultra integrations that rely on UEF** <br/> > **Review UPDATE in LTI 1.3 section. This post previously mentioned a bug that no longer exists.**
Here is a brief description of the contributing factors:

Expand Down Expand Up @@ -47,11 +46,11 @@ If you are a developer that has built a UEF integration, we actually implemented

This one-time session cookie is added to the claims in the LTI 1.3 JWT and the form POST parameters in LTI 1.1. You can grab that value from the LTI launch, return it as a parameter in your 3LO authorization code request, and your problem will be solved.

UPDATE: This section previously mentioned a bug where the userId needed to be appended to the one_time_session token. This bug has been fixed. Your code can now use the one_time_session_token as provided by Blackboard Learn without appending the userId. Blackboard no longer appends a userId, nor expects it in the returned value. If your code does append a comma and userId, that’s OK, you don’t immediatly need to change your code it as Blackboard just ignores the comma and what comes after if those are part of the value you send back.
UPDATE: This section previously mentioned a bug where the userId needed to be appended to the one_time_session token. This bug has been fixed. Your code can now use the one_time_session_token as provided by Blackboard Learn without appending the userId. Blackboard no longer appends a userId, nor expects it in the returned value. If your code does append a comma and userId, that’s OK, you don’t immediatly need to change your code it as Blackboard just ignores the comma and what comes after if those are part of the value you send back.

### LTI 1.3

In LTI 1.3, you will see the value in the `https://blackboard.com/lti/claim/one_time_session_token` claim. This token is made up of a specially generated token value. Here's a Python 3 code snippet to illustrate how this might look.
In LTI 1.3, you will see the value in the `https://blackboard.com/lti/claim/one_time_session_token` claim. This token is made up of a specially generated token value. Here's a Python 3 code snippet to illustrate how this might look.

```
    # Get the value of the one time session token from the LTI claim
Expand Down
4 changes: 2 additions & 2 deletions blog/2022/2022-08-12-DevCon2022.md
Original file line number Diff line number Diff line change
@@ -1,12 +1,13 @@
---
slug: DevCon-2022-Presentations!
title: DevCon 2022 Presentations!
authors:
authors:
- name: Davey Herrera
title: Software Engineer, R&D User Experience
tags: ["devcon", "community", "recap", "2022"]
hide_table_of_contents: false
---

<!-- ---
slug: welcome-docusaurus-v2
authors:
Expand All @@ -23,7 +24,6 @@ image: https://i.imgur.com/mErPwqL.png
hide_table_of_contents: false
--- -->


# DevCon 2022 Presentations!

We will be adding sessions here as soon as we get the presentations! If you want to see your DevCon presentation, please write us at [email protected]. All times are in ET.
Expand Down
3 changes: 1 addition & 2 deletions blog/2024/2024-03-15-bestpractices-emailsupport.md
Original file line number Diff line number Diff line change
Expand Up @@ -49,5 +49,4 @@ Below are the recommended best practices to ensure you receive the quickest, mos
We eagerly anticipate receiving full support and collaborating with your teams to ensure a successful integration.


Cheers!
<AuthorBox frontMatter={frontMatter}/>
Cheers!
7 changes: 3 additions & 4 deletions blog/2024/2024-04-18-public-rest-api-and-roadmap.md
Original file line number Diff line number Diff line change
@@ -1,10 +1,10 @@
---
slug: public-rest-api-and-dev-portal-roadmap-april-2024
title: Public Rest API and devportal roadmap April 2024
published: '2024-04-18'
edited: '2024-04-18'
published: "2024-04-18"
edited: "2024-04-18"
author: Camilo Dominguez
tags: ['bestpractices', 'Integrations', 'Partners', 'Developers', 'Community']
tags: ["bestpractices", "Integrations", "Partners", "Developers", "Community"]
hide_table_of_contents: true
---

Expand All @@ -19,4 +19,3 @@ Here is the slide deck!
<object data="/assets/files/Public_REST_API_Roadmap_april_2024.pdf" width="100%" height="600" type="application/pdf" ></object>

Cheers!
<AuthorBox frontMatter={frontMatter}/>
2 changes: 1 addition & 1 deletion docs/archive/b2/resources/prepare-for-java11.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ Deployed in February 2020.

When collecting updated Building Blocks, make sure you have the latest version of the B2 from the provider (vendor, open source, or internal). Check vendor websites or contact vendors’ support and get the latest versions of B2s from them. Confirm that the updates have been tested to be Java 11 compatible and validate in your test or stage environment. For open source Building Blocks you use, check community sources such as [OSCELOT](https://github.com/oscelot) to see if updates are available. If you have B2s created by Blackboard Consulting and supported under an ICM contract, contact Blackboard Product Support for the latest version that is Java 11 compatible.

3. **Transition integrations to different integration types**. Some solution providers have transitioned their integrations to other methods, such as leveraging the [Learning Tools Interoperability (LTI) standard](https://imsglobal.org/lti) or [REST APIs](/docs/blackboard/rest-apis/getting-started/first-steps.md) instead of Building Block APIs. In some cases, they may have completely different B2 integrations than the one you’re using. Working with these vendors, determine whether this is appropriate for you. Examples of these integrations requiring transition include Lynda.com and Turning Technologies.
3. **Transition integrations to different integration types**. Some solution providers have transitioned their integrations to other methods, such as leveraging the [Learning Tools Interoperability (LTI) standard](https://www.1edtech.org/standards/lti) or [REST APIs](/docs/blackboard/rest-apis/getting-started/first-steps.md) instead of Building Block APIs. In some cases, they may have completely different B2 integrations than the one you’re using. Working with these vendors, determine whether this is appropriate for you. Examples of these integrations requiring transition include Lynda.com and Turning Technologies.

4. **Test and update in-house Building Blocks**. If you have B2s created at your institution, you should confirm their functionality in test/stage and prepare to update them. Guidance about updating Building Blocks can be found [here](preparing-for-saas-and-new-learn-versions.md). We’ve created an automated tool to assist with identifying potential library incompatibilities. While this tool doesn’t necessarily inform you of the functional behavior of the Building Block with Java 11, it provides guidance around library incompatibilities that could lead to a non-functional B2. See the section about the Building Block Scan Tool in the Resources section below.

Expand Down
7 changes: 0 additions & 7 deletions docs/blackboard/caliper/caliper-intro.md

This file was deleted.

Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ Caliper Analytics is an IMS Global standard focused on the delivery of
consistent event tracking across campus applications.

For more information on
the Caliper Analytics specification, visit the IMS site [here](https://www.imsglobal.org/caliper).
the Caliper Analytics specification, visit the IMS site [here](https://www.1edtech.org/standards/caliper).

Caliper is implemented in Learn as the Learn Activity Stream. This
data is stored in an external system called the Caliper Event Store. This
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ the use of common tools across platforms with the added ability to analyze the
usage of that tool for all students regardless of the environment that student
originates from.

We also have documentation on the [specific events sent](../events/event-guide.md) by Learn,
We also have documentation on the [specific events sent](./events/event-guide.md) by Learn,

The metric profiles are realized in the form of JSON for Linked Data (JSON-LD)
payloads containing a set of common objects, each with the ability to add
Expand Down
1 change: 1 addition & 0 deletions docs/blackboard/lti/1.1/welcome.md
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
LTI 1.1
Loading

0 comments on commit aa7dce8

Please sign in to comment.