adobedocs / adobe-dev-console Goto Github PK

This is not an implementation issue, but an issue of the content. There is still no correct documentation that I can find on your website about authenticating the aio cli with the servertoserver authentication.

I had to find a hack in this github issue: adobe/aio-cli-plugin-cloudmanager#676

There is also a ticket that has been up for almost a year here: adobe/aio-cli-plugin-cloudmanager#676

I am not sure why you have listed the JWT method as deprecated but not included an actual solution for the 'current' solution.

By the last commit dates, you're not maintaining this anymore, however, under the prerequisite section of the readme:

1. There's a choice of "Web app" or "Single-Page App" - Which one?
2. I cannot set the redirect URL to https://localhost:8000:

Please update your documentation.

Thanks

Expected Behaviour

Edits to oauth redirect urls are saved

Actual Behaviour

An error is returned. The response from the server is

{
    "errors": [
        {
            "message": "Variable \"$input\" got invalid value { redirectUriList: [\"REDACTED\"], defaultRedirectUri: \"REDACTED\", domain: null, platform: \"Web\" }; Field name of required type String! was not provided.",
            "locations": [
                {
                    "line": 1,
                    "column": 69
                }
            ],
            "extensions": {
                "code": "BAD_USER_INPUT"
            }
        },
        {
            "message": "Variable \"$input\" got invalid value { redirectUriList: [\"REDACTED\"], defaultRedirectUri: \"REDACTED\", domain: null, platform: \"Web\" }; Field description of required type String! was not provided.",
            "locations": [
                {
                    "line": 1,
                    "column": 69
                }
            ],
            "extensions": {
                "code": "BAD_USER_INPUT"
            }
        }
    ]
}

Reproduce Scenario (including but not limited to)

https://developer.adobe.com/console/projects/REDACTED/REDACTED/credentials/REDACTED/details

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

Expected Behaviour

Actual Behaviour

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

Expected Behaviour

Actual Behaviour

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

Expected Behaviour

On the Service Account (JWT)
DEPRECATED](https://developer.adobe.com/developer-console/docs/guides/email-alerts/cert-expiry/) page, on Step 2, task 2, it states to "Go to the Service Account (JWT) tab"

Actual Behaviour

When I go to that task, it is now replaced with "Service Account (JWT) DEPRECATED." Drilling down further, it speaks to how JWT is being deprecated and being replaced by OAuth. It's not clear how to refresh an expiring certificate under that circumstance.

Reproduce Scenario (including but not limited to)

Steps to Reproduce

1. Go to https://developer.adobe.com/developer-console/docs/guides/email-alerts/cert-expiry/
2. Notice that it now says Service Account (JWT)
   DEPRECATED
3. Choose that and see completely different instructions than what the documentation indicates.
   

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

Expected Behaviour

Actual Behaviour

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

Expected Behaviour

Code should compile and run

Actual Behaviour

The current sample code generates three errors:

1. “Argument 1:cannot convert from ‘RestSharp.Method’ to ‘string?’” <- syntax error reported for line 52 of Program.cs (where it says "var request = new RestRequest(Method.POST);").

2. "The type or namespace ‘IRestResponse’ could not be found (are you missing a using directive or an assembly reference?)” <-- syntax error reported for line 62 of Program.cs (where it says "“IRestResponse response = client.Execute(request);”").

3. "An error has occured: The format of value 'multipart/form-data; boundary=----boundary' is invalid" <-- runtime error generated seemingly for the parameter added via line 55 (via a request.AddParameter() method call).

Reproduce Scenario (including but not limited to)

Simply try to compile and run.

Steps to Reproduce

For the first two errors, simply try to compile.
For the third error, you'd need to tweak the code (as a workaround to get it to compile) ... but then run the program.

Platform and Version

Windows 10 running Microsoft Visual Studio 2019.

Sample Code that illustrates the problem

Current code leveraging the latest version of the RestSharp library (i.e., v108.0.2).

NOTE: All three of these issues can be resolved by instead leveraging the old 106.13.0 version of the RestSharp library; however, for vulnerability reduction reasons, we need to be using the latest version of all such open source libraries. Additional information can be found at the RestSharp documentation page (https://restsharp.dev/intro.html#introduction) which says, "WARNING - RestSharp v107 changes the library API surface and its behaviour significantly. We advise looking at v107 docs to understand how to migrate to the latest version of RestSharp.".

Logs taken while reproducing problem

n/a

Expected Behaviour

The given curl command should delete an existing client secret based on the UUID provided.

Actual Behaviour

Returns "403 Forbidden"

Reproduce Scenario (including but not limited to)

Deleting an old client secret while performing client secret rotation on a project.

Suggested Fix:

Update the curl method to DELETE on line 144 of src/pages/guides/authentication/ServerToServerAuthentication/implementation.md as below.

curl -X DELETE 'https://api.adobe.io/console/organizations/{orgId}/credentials/{credentialId}/secrets/{uuid from step 9}' \
     -H 'Authorization: Bearer {ACCESS TOKEN GENERATED IN STEP 5}'
     -H 'x-api-key: {CLIENT ID FROM STEP 6}'

Steps to Reproduce

1. Follow the steps 1-9 in src/pages/guides/authentication/ServerToServerAuthentication/implementation.md to create a client secret
2. On step 10, Run the below curl command provided in documentation to delete an existing client secret.

curl -X POST 'https://api.adobe.io/console/organizations/{orgId}/credentials/{credentialId}/secrets/{uuid from step 9}' \
     -H 'Authorization: Bearer {ACCESS TOKEN GENERATED IN STEP 5}'
     -H 'x-api-key: {CLIENT ID FROM STEP 6}'

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

API example on Step 10 in "Rotating client secrets programmatically" uses the wrong method. POST should be updated to DELETE
Currently the code sample is:

curl -X POST 'https://api.adobe.io/console/organizations/{orgId}/credentials/{credentialId}/secrets/{uuid from step 9}' \
     -H 'Authorization: Bearer {ACCESS TOKEN GENERATED IN STEP 5}'
     -H 'x-api-key: {CLIENT ID FROM STEP 6}'`

However, it should be:

curl -X DELETE 'https://api.adobe.io/console/organizations/{orgId}/credentials/{credentialId}/secrets/{uuid from step 9}' \
     -H 'Authorization: Bearer {ACCESS TOKEN GENERATED IN STEP 5}'
     -H 'x-api-key: {CLIENT ID FROM STEP 6}'

Hi,

Whenever I am doing polling to asset I am getting bad address Error.
Can anyone suggest me how I can resolve that.

error
{'error': {'code': 'BAD_ADDRESS', 'message': 'Bad Address, request terminated; requestId=xxxxxxxxxxxxxxxx', 'status': 400}, 'status': 'failed'}

After setting up Server to Server Authentication and then clicking on "Connect another service", some services such as Lightroom, have a "Requires Adobe Review" blue box and the ability to add them is disabled. There is no documentation on how to initiate this review. (Or if its even possible)

It would be extremely beneficial to be able to use client_credentials grant type with Adobe Lightroom and not have to use web-based authentication. I don't understand why Photoshop is allowed to be connected this way, but Lightroom is not.

I understand I can create a logon redirect, and then hold the refresh token on the server, and keep refreshing forever. But if that loses access then it forces me/the user to log back on to click some buttons.

I would like to get an example curl command, with actual values and not placeholders, to see how to get the token using curl.

Expected Behaviour

To improve the onboarding experience for users creating an app builder project for Adobe I/O Events via Adobe Developer Console, we want the Adobe Services I/O Management API (Step 6) to be automatically added/configured if the user adds Adobe I/O Events for Adobe Commerce API (Step 9) to the app builder project.

Step 6

Step 9

Note - Remove Step 6 from the process of creating an app builder project for Adobe I/O Events.

Actual Behaviour

Now, if the user wants to create an app builder project for Adobe I/O Events, they need to perform all the following steps

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

Hi,
I'm facing a significant problem with the Adobe Embed PDF API on mobile devices. Despite setting the default view mode to "FIT_WIDTH" in the preview configuration, the PDF width appears too small on phone screens. This issue is not encountered on desktops.

Google and Edge browsers adjust the PDF width perfectly on mobile devices when using their built-in PDF viewer.

Could you please provide guidance on resolving this issue?
here is my code:
const previewConfig = {
defaultViewMode: "FIT_WIDTH",
showDownloadPDF: false,
showZoomControl: true,
showAnnotationTools: false

}

var adobeDCView = new AdobeDC.View({ clientId: "your_id", divId: "adobe-dc-view" });
adobeDCView.previewFile({
content: { location: { url: pdfUrl } },
metaData: { fileName: pdfUrl }
}, previewConfig);

// Use PDF.js to read the name from the PDF
var loadingTask = pdfjsLib.getDocument(pdfUrl);
loadingTask.promise.then(function (pdf) {
pdf.getPage(1).then(function (page) { // Assuming the name is on the first page
page.getTextContent().then(function (textContent) {
// Process textContent to find the name
// This is a simplified example and may need more logic to find the correct text

     });
 });

}, function (reason) {
console.error(reason);
});

Expected Behaviour

We are looking for

Actual Behaviour

1. The underlying connection was closed: An unexpected error occurred on a send
   PS E:\exe\ErrorDrillDown\adobe_test\adobe_test> .\ConsoleAppTest.exe
   Enter any key to start
   Start of Process
   Getting file names
   Getting credentials
   proceeding to executionContext
   proceeding to createPdfOperation
   Assigning doc file to file reference
   Setting input
   Starting to execute pdf operation
   Error response received for the request: The underlying connection was closed: An unexpected error occurred on a send.
   at Adobe.DocumentCloud.Services.core.http.HttpClient.ExecuteRequest[T](HttpBaseRequest baseRequest)
   at Adobe.DocumentCloud.Services.core.http.HttpClient.<>c__DisplayClass11_01.<Execute>b__0() at Polly.Policy1.<>c__DisplayClass11_0.b__0(Context ctx, CancellationToken ct)
   at Polly.Retry.RetryEngine.Implementation[TResult](Func3 action, Context context, CancellationToken cancellationToken, ExceptionPredicates s houldRetryExceptionPredicates, ResultPredicates1 shouldRetryResultPredicates, Action4 onRetry, Int32 permittedRetryCount, IEnumerable1 sleepD
   urationsEnumerable, Func4 sleepDurationProvider) at Polly.Retry.RetryPolicy1.Implementation(Func3 action, Context context, CancellationToken cancellationToken) at Polly.Policy1.Execute(Func3 action, Context context, CancellationToken cancellationToken) at Polly.Policy1.Execute(Func1 action) at Adobe.DocumentCloud.Services.core.http.HttpClient.Execute[T](HttpBaseRequest baseRequest) at Adobe.DocumentCloud.Services.core.api.CPFApi.CPFPredictApi[T](InternalExecutionContext context, ContentAnalyzerRequestsDto contentAnalyzer RequestsDto, List1 sourceFileRefList)
   at Adobe.DocumentCloud.Services.core.api.CreatePDFApi.ConvertToPdf(InternalExecutionContext context, FileRefImpl sourceFileRef, CreatePDFOpti
   ons createPdfOptions)
   at Adobe.DocumentCloud.Services.pdfops.CreatePDFOperation.Execute(ExecutionContext context)
   at ConsoleAppTest.Program.Main(String[] args) in C:\Users\61380\source\repos\ConsoleAppTest\ConsoleAppTest\Program.cs:line 76
   Adobe.DocumentCloud.Services

2. We tried to use the adobe login and got error

Error response received for the request: The SSL connection could not be established, see inner exception. Unable to read data from the transpor
t connection: An existing connection was forcibly closed by the remote host..

PS E:\exe\ErrorDrillDown\adobe_core_test_09032022_1\adobe_core_test> .\Adobe_core.exe
Enter any key to start
Start of Process
Getting file names
Getting credentials
proceeding to executionContext
proceeding to createPdfOperation
Assigning doc file to file reference
Setting input
Starting to execute pdf operation
Error response received for the request: The SSL connection could not be established, see inner exception. Unable to read data from the transpor
t connection: An existing connection was forcibly closed by the remote host..
at Adobe.DocumentCloud.Services.core.http.HttpClient.ExecuteRequest[T](HttpBaseRequest baseRequest)
at Adobe.DocumentCloud.Services.core.http.HttpClient.<>c__DisplayClass11_01.<Execute>b__0() at Polly.Policy1.<>c__DisplayClass11_0.b__0(Context ctx, CancellationToken ct)
at Polly.Retry.RetryEngine.Implementation[TResult](Func3 action, Context context, CancellationToken cancellationToken, ExceptionPredicates s houldRetryExceptionPredicates, ResultPredicates1 shouldRetryResultPredicates, Action4 onRetry, Int32 permittedRetryCount, IEnumerable1 sleepD
urationsEnumerable, Func4 sleepDurationProvider) at Polly.Retry.RetryPolicy1.Implementation(Func3 action, Context context, CancellationToken cancellationToken) at Polly.Policy1.Execute(Func3 action, Context context, CancellationToken cancellationToken) at Polly.Policy1.Execute(Func1 action) at Adobe.DocumentCloud.Services.core.http.HttpClient.Execute[T](HttpBaseRequest baseRequest) at Adobe.DocumentCloud.Services.core.api.CPFApi.CPFPredictApi[T](InternalExecutionContext context, ContentAnalyzerRequestsDto contentAnalyzer RequestsDto, List1 sourceFileRefList)
at Adobe.DocumentCloud.Services.core.api.CreatePDFApi.ConvertToPdf(InternalExecutionContext context, FileRefImpl sourceFileRef, CreatePDFOpti
ons createPdfOptions)
at Adobe.DocumentCloud.Services.pdfops.CreatePDFOperation.Execute(ExecutionContext context)
at Adobe_core.Program.Main(String[] args) in C:\Users\61380\source\repos\Adobe_core\Adobe_core\Program.cs:line 79
Adobe.DocumentCloud.Services

Reproduce Scenario (including but not limited to)

  We are trying to merge PDF which is not happening. we are getting connection closed error. It is working in local but not working in the server.

Steps to Reproduce

Platform and Version

.Net windows service

Sample Code that illustrates the problem

string StartService = ConfigurationManager.AppSettings["AdobeStartService"];
if (StartService == "true")
{
string privatekey = File.ReadAllText(AppDomain.CurrentDomain.BaseDirectory + "/private.key"); //changes made by Nallasivan/Rahul/Chandana/uncommented the adobe service
string jsoncredentials = File.ReadAllText(AppDomain.CurrentDomain.BaseDirectory + "/pdfservices-api-credentials.json");
PrivateKey jsoncred = JsonConvert.DeserializeObject(jsoncredentials);
Credentials credentials = Credentials.ServiceAccountCredentialsBuilder()
.WithAccountId(jsoncred.account_id)
.WithClientId(jsoncred.client_id)
.WithClientSecret(jsoncred.client_secret)
.WithOrganizationId(jsoncred.organization_id)
.WithPrivateKey(privatekey).Build();
ExecutionContext executionContext = ExecutionContext.Create(credentials);
CreatePDFOperation createPdfOperation = CreatePDFOperation.CreateNew();
// Set operation input from a source file.
FileRef source = FileRef.CreateFromLocalFile(docPath);
createPdfOperation.SetInput(source);
// Execute the operation.
FileRef result = createPdfOperation.Execute(executionContext);
// Save the result to the specified location.
result.SaveAs(DestinationPDFFilePath);
/* PDF conversion Ends */
}

Logs taken while reproducing problem

  Attached in the ticket

Expected Behaviour

Actual Behaviour

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

New one

Issue in /src/pages/guides/authentication/JWT/index.md
Users receive a 404 when clicking the embedded link for 'Create a public key certificate'.
https://www.adobe.io/developer-console/docs/guides/authentication/AuthenticationOverview/ServiceAccountIntegration.md#step-2-create-a-public-key-certificate

I am not understanding how to actually use the new oauth credential in my AEM integrations. Do I still use IMS? If so, what do I put for my token? I can't find where that is...

Expected Behaviour

Actual Behaviour

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

Issue in /src/pages/guides/authentication/ServiceAccountIntegration.md

It looks like two image references are broken in Step 3: Try it!

Issue in /src/pages/guides/authentication/APIKeyIntegration.md

When the API has been successfully connected, you will be able to access the newly generated API Key.

But there is no field with the label API key on the console page. Maybe you mean CLIENTID?

once a day... all PDF Services in Power Automate failed... spent 4 hours searching or an issue...

what to do?

Body - Errors:
"error": {
"code": "InvalidParameter",
"message": "Unsupported Input File Type"
}
}

Headers:
{
"Transfer-Encoding": "chunked",
"x-request-id": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"pragma": "no-cache",
"x-content-type-options": "nosniff",
"strict-transport-security": "max-age=31536000; includeSubdomains",
"x-robots-tag": "noindex,nofollow",
"vary": "accept-encoding",
"Timing-Allow-Origin": "*",
"x-ms-apihub-cached-response": "false",
"x-ms-apihub-obo": "false",
"Cache-Control": "no-store, must-revalidate, no-cache",
"Date": "Mon, 13 Mar 2023 13:39:02 GMT",
"Content-Type": "application/json",
"Expires": "Thu, 01 Dec 1994 16:00:00 GMT",
"Content-Length": "102"

Issue in /src/pages/guides/getting-started.md

Issue in /src/pages/support/faq.md

Expected Behaviour

Actual Behaviour

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

Expected Behaviour

Actual Behaviour

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

The OAuth-Server-to-Server migration is successful. The credentials have changed from the service account. This is the guide used:
https://developer.adobe.com/developer-console/docs/guides/authentication/ServerToServerAuthentication/migration/

Following the steps outlined in the Adobe.io documentation, I generated a JWT access token. However, when attempting to exchange the JWT for a Bearer Access Token using the provided request:
‘curl -X POST
https://ims-na1.adobelogin.com/ims/exchange/jwt/?client_id=<Adobe.IO API KEY>&client_secret=<Adobe.IO Client Secret>&jwt_token=JWT_TOKEN’
I encountered an internal server error. A "500 Internal Server Error" indicates that there's an issue on the server side, and it's a generic error message that doesn't provide specific details about the problem. I tried it on the terminal window and Postman. Looks like an issue with the Adobe Server.
{
"error": "internal_error",
"error_description": "Please try again later"
}
I'm also interested in understanding whether we can manually add/modify scopes within our credentials, for ex: exchange_jwt scope

Expected Behaviour

I would like to edit an A/B activity in the UI created through the latest Admin APIs (v3)

Actual Behaviour

When an activity is created through API, the option to edit is not available in the UI.

Steps to Reproduce

1. Create a new A/B activity using the admin API - https://developer.adobe.com/target/administer/admin-api/#tag/Activities/operation/createActivity_4_1
2. When the activity is created in Target, go to the activity from the UI console.
3. There is no option to edit the activity.

Platform and Version

Version of API: v3

Expected Behaviour

The sample code is supposed to build a JWT object and then pass it in an Adobe API call to get back an "access token".

Actual Behaviour

Such API calls are failing with a response.ErrorMessage of "The remote server returned an error: (407) Proxy Authentication Required."

However, from that error message, I can't tell if the "remote server" is referring to the ims-na1.adobelogin.com site (to which I'm sending the request) or if it's referring to some proxy server of my own company (which might be blocking the request before it even leaves my company's internal network).

Reproduce Scenario (including but not limited to)

Use the sample code to make the API call.
NOTE: I successfully get an Access Token when I copy-paste my Adobe API Project's private key into the GUI box provided for such testing at https://developer.adobe.com/console/projects/374378/4566206088344859311/apis/AdobeIOManagementAPISDK/details.

Steps to Reproduce

1. Prepare the requisite Adobe API "Project" (e.g., https://developer.adobe.com/console/projects/374378/4566206088344859311/overview)
2. Use that project to provide the necessary arguments for (using the sample code to make a) REST API call ... leveraging an older version of the RestSharp open source library (e.g., v106.13.0) due to another issue (#50)

Platform and Version

Windows 10 running Microsoft Visual Studio 2019.

Sample Code that illustrates the problem

Current code leveraging an older version of the RestSharp library (e.g., v106.13.0).

Logs taken while reproducing problem

n/a

https://github.com/frappe/erpnext/releases/tag/v14.13.0

Expected Behaviour

As per the console information, multiple domains are allowed per API KEY (up to 5 domains).

Actual Behaviour

If we configure only one domain, it works.

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

Expected Behaviour

The sample code is supposed to build a JWT object and then pass it in an Adobe API call to get back an "access token".

Actual Behaviour

Such API calls are failing with a response.Content of: "{"error_description":"The metascopes in the JWT are not a subset of the metascopes in the binding.","error":"invalid_scope"}"

Reproduce Scenario (including but not limited to)

Use the sample code to make the API call.
NOTE: I successfully get an Access Token when I copy-paste my Adobe API Project's private key into the GUI box provided for such testing at https://developer.adobe.com/console/projects/374378/4566206088344859311/apis/AdobeIOManagementAPISDK/details.

Steps to Reproduce

1. Prepare the requisite Adobe API "Project" (e.g., https://developer.adobe.com/console/projects/374378/4566206088344859311/overview)
2. Use that project to provide the necessary arguments for (using the sample code to make a) REST API call ... leveraging an older version of the RestSharp open source library (e.g., v106.13.0) due to another issue (#50)

Platform and Version

Windows 10 running Microsoft Visual Studio 2019.

Sample Code that illustrates the problem

Current code leveraging an older version of the RestSharp library (e.g., v106.13.0).

Logs taken while reproducing problem

n/a

Hello,
we are encountering problems with our connections to Creative Cloud Libraries.
Since recently all our connections are being disconnected.

The creation of the connection itself is successful.
However, the connection is not active.

We check if the connection is active via this url: https://cc-libraries.adobe.io/api/v1/libraries/
In the logs we find that an 401 (Unauthorized) causes this error.

We recreated the request in postman to get further details of the error. The error-message we received is the following:

{
    "reason": "There was an error processing your request. Request id: C0SrDhM2OqQD60LNtOOXPnYH5hFcsUJe.",
    "message": "System error"
}

There were no changes in our code that would affect the Creative Cloud Libraries-integration. We checked if all Keys, Secrets and Variables are set correctly.

This is the request we sent via postman:

"request": {
	"method": "GET",
	"header": [
		{
			"key": "Authorization",
			"value": "Bearer *****",
			"type": "text"
		},
		{
			"key": "x-api-key",
			"value": "*****",
			"type": "text"
		}
	],
	"url": {
		"raw": "https://cc-libraries.adobe.io/api/v1/libraries?limit=1",
		"protocol": "https",
		"host": [
			"cc-libraries",
			"adobe",
			"io"
		],
		"path": [
			"api",
			"v1",
			"libraries"
		],
		"query": [
			{
				"key": "limit",
				"value": "1"
			}
		]
	},
},

We appreciate you help with this error.

Best wishes

Issue in /src/pages/guides/authentication/ServerToServerAuthentication/implementation.md :
It's a small thing, but the top paragraph states
"The following guide goes over finer implementation details for OAuth Server-to-Server credentials. At the end of the guide is a list of recommended industry-standard OAuth2 libraries. Before you proceed, we recommend you become familiar with the server to server authentication credentials in our server to server authentication guide."

That last link just points to the page we're currently on. I'm not sure if it's supposed to point to other documentation, or if it was copied from elsewhere, but it's a little confusing to be told "before you proceed with this documentation, review this documentation".