> For the complete documentation index, see [llms.txt](https://docs.aqua-cloud.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aqua-cloud.io/documentation/product-updates-for-public-and-private-clouds-customers/release-notes/2022/22.132.0-public-and-private-clouds.md).

# 22.132.0 - public and private clouds

Discover what's new in version 22.132.0: enhanced authentication options, a revamped knowledge base, onboarding improvements, and key bug fixes for public and private clouds.

## Release notes

Version  22.132.0

Include all changes since 22.123.0 version

<mark style="color:green;">New features and improvements:</mark>

RQ048073 -  Authentification | Option to disable internal aqua password when LDAP/SAML/oAuth is set up

RQ048126 - New knowledge base in aqua

RQ048034 - User onboarding | Account set-up and short intro video

<br>

<mark style="color:red;">Fixed defects:​​​​</mark>

DF048520 - Agile | Backlog and Kanban board | Loading time of the board takes \~10 seconds&#x20;

DF048548 - Getting unexpectedly logged out every 15 mins

DF048537 - Test Scenarios Execution | Execution can not be aborted

DF048654 - Test Case Execution | Execution can not be aborted

DF048668 - Preview of the videos doesn’t work


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.aqua-cloud.io/documentation/product-updates-for-public-and-private-clouds-customers/release-notes/2022/22.132.0-public-and-private-clouds.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.