WEBVTT

1
00:00:00.000 --> 00:00:02.342
Harbour Roads Training wants another program to

2
00:00:02.345 --> 00:00:05.713
use supported platform features. Normal browser uploads

3
00:00:05.716 --> 00:00:08.352
do not require an API connection key;

4
00:00:08.355 --> 00:00:11.208
this lesson is for integration setup. Connections

5
00:00:11.351 --> 00:00:14.105
lists named keys and their short references.

6
00:00:14.546 --> 00:00:17.257
An authorised user can create or disable

7
00:00:17.272 --> 00:00:19.643
keys according to the permissions available to

8
00:00:19.658 --> 00:00:22.021
them. Choose a name that identifies the

9
00:00:22.031 --> 00:00:25.002
program and purpose, such as Training import

10
00:00:25.012 --> 00:00:28.546
service. A useful label helps later investigation

11
00:00:28.557 --> 00:00:31.042
and retirement. A newly created key is

12
00:00:31.054 --> 00:00:34.003
shown once. Transfer it through your approved

13
00:00:34.016 --> 00:00:37.541
secret-management process, not in a training video,

14
00:00:37.553 --> 00:00:41.188
source-code repository, email thread or screenshot. Our

15
00:00:41.193 --> 00:00:43.901
training screen never reveals a usable token.

16
00:00:44.017 --> 00:00:46.912
It shows only a deliberately invalid placeholder,

17
00:00:46.916 --> 00:00:49.396
clearly labelled as an example. The short

18
00:00:49.409 --> 00:00:51.735
key reference identifies the record in the

19
00:00:51.748 --> 00:00:54.157
table. It is not the bearer secret

20
00:00:54.171 --> 00:00:56.162
and cannot be used as a substitute

21
00:00:56.175 --> 00:00:58.049
for the full key. Use the API

22
00:00:58.054 --> 00:01:00.599
documentation for the current supported endpoints and

23
00:01:00.904 --> 00:01:03.898
authentication format. Do not assume every browser

24
00:01:03.903 --> 00:01:06.790
action has an equivalent public API. Start

25
00:01:06.803 --> 00:01:09.176
with an authorised test organisation and a

26
00:01:09.188 --> 00:01:12.959
small, non-sensitive example. Confirm the response and

27
00:01:12.971 --> 00:01:15.920
expected scope before connecting a production data

28
00:01:15.932 --> 00:01:18.857
flow. The created and last-used information can

29
00:01:18.867 --> 00:01:22.050
help identify an unused or unexpected connection.

30
00:01:22.539 --> 00:01:25.562
Investigate with the responsible integration owner before

31
00:01:25.572 --> 00:01:28.644
changing access. Disabling a key stops programs

32
00:01:28.651 --> 00:01:30.984
using it. Plan the change and update

33
00:01:30.984 --> 00:01:33.618
the integration where necessary, then confirm the

34
00:01:33.624 --> 00:01:36.147
old key is no longer needed. Pause

35
00:01:36.260 --> 00:01:39.800
here. Name a training integration, describe where

36
00:01:39.821 --> 00:01:42.357
its secret belongs, and explain why a

37
00:01:42.470 --> 00:01:45.279
screen recording must never include the usable

38
00:01:45.301 --> 00:01:46.192
token.