> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/sso-connect-on-prem/upgrading-sso-connect.md).

# Upgrading SSO Connect On-Prem

Instructions for upgrading your Keeper SSO Connect On-Prem Service

Keeper Security performs security updates to Keeper SSO Connect On-Prem.

### Regular Upgrades

If you are performing a regular update of SSO Connect On-Prem (from a recent version):

* Open the Admin Console and visit the privisioning tab of the node
* Download, unzip and run the installer

***

### Upgrading from a Legacy Version

Follow the instructions in the [Legacy Update](/sso-connect-on-prem/update-instructions.md) page to proceed with the upgrade if you are using a very old pre-v17 version of SSO Connect On-Prem.

***

#### Need Help?

If you are not familiar with your environment or if you are not comfortable performing the update, please [contact Keeper support](https://www.keepersecurity.com/support.html).

Before you contact support, please provide the following information:

* SSO Connect Version
* SSO Connect server OS version
* Identity Provider name and version
* Java version
* Any other network configuration (e.g. HA, Firewall, NGINX, etc)


---

# 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.keeper.io/sso-connect-on-prem/upgrading-sso-connect.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.