Skip to content

[docs] feat(csrf): add breaking change for csrf (#287)#288

Open
gabriel-peze wants to merge 1 commit intomainfrom
issue/287
Open

[docs] feat(csrf): add breaking change for csrf (#287)#288
gabriel-peze wants to merge 1 commit intomainfrom
issue/287

Conversation

@gabriel-peze
Copy link
Copy Markdown
Contributor

@gabriel-peze gabriel-peze commented Apr 23, 2026

Add CSRF breaking changes

Closes #287


!!! info ""

* **Introduced in**: `OpenAEV 2.3.3`
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* **Introduced in**: `OpenAEV 2.3.3`
* **Introduced in**: `OpenAEV 2.3.4`


## Description of changes

Starting with **OpenAEV 2.3.3**, API calls initiated from the **OpenAEV frontend** must include a valid **CSRF token**.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Starting with **OpenAEV 2.3.3**, API calls initiated from the **OpenAEV frontend** must include a valid **CSRF token**.
Starting with **OpenAEV 2.3.4**, API calls initiated from the **OpenAEV frontend** must include a valid **CSRF token**.


!!! warning

Do not run mixed versions in production (for example: OpenAEV `2.3.3` with older injectors or collectors). Upgrade all components in the same maintenance window.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Do not run mixed versions in production (for example: OpenAEV `2.3.3` with older injectors or collectors). Upgrade all components in the same maintenance window.
Do not run mixed versions in production (for example: OpenAEV `2.3.4` with older injectors or collectors). Upgrade all components in the same maintenance window.

For more details, see [this migration guide](breaking-changes/2.0.0-openaev-renaming.md) No newline at end of file
For more details, see [this migration guide](breaking-changes/2.0.0-openaev-renaming.md)

## OpenAEV 2.3.3
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
## OpenAEV 2.3.3
## OpenAEV 2.3.4


#### OpenAEV CSRF protection for frontend API calls

Starting with **OpenAEV 2.3.3**, frontend-initiated API calls must include a valid CSRF token.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Starting with **OpenAEV 2.3.3**, frontend-initiated API calls must include a valid CSRF token.
Starting with **OpenAEV 2.3.4**, frontend-initiated API calls must include a valid CSRF token.

#### OpenAEV CSRF protection for frontend API calls

Starting with **OpenAEV 2.3.3**, frontend-initiated API calls must include a valid CSRF token.
To prevent API authentication and connection issues, make sure all ecosystem components are upgraded to versions compatible with OpenAEV 2.3.3.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
To prevent API authentication and connection issues, make sure all ecosystem components are upgraded to versions compatible with OpenAEV 2.3.3.
To prevent API authentication and connection issues, make sure all ecosystem components are upgraded to versions compatible with OpenAEV 2.3.4.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add a breaking change to explain about the CSRF

2 participants