---
title: Unable to use CLI after Platform 2.10 upgrade
description: Prelude made major changes to the platform authentication the week of March 24 2025.  This included the deprecation of legacy token based authentication.  In the weeks before the update, Prelude asked
---

[Skip to content](https://support.preludesecurity.com/unable-to-use-cli-after-platform-2.10-upgrade#main-content)

English

Show submenu for translations

[Contact support](https://support.preludesecurity.com/kb-tickets/new?hsLang=en)

![Prelude\_Wordmark\_Black\_Transparent.png\]](https://support.preludesecurity.com/hs-fs/hubfs/Prelude_Wordmark_Black_Transparent.png?height=50&name=Prelude_Wordmark_Black_Transparent.png)

Open main navigation

Close main navigation

- English
  
  Show submenu for translations
- [Contact support](https://support.preludesecurity.com/kb-tickets/new)
- [Visit the website](https://www.preludesecurity.com/)

[Visit the website](https://www.preludesecurity.com/)

 Find what you're looking for

- There are no suggestions because the search field is empty.

1. [Knowledge Base](https://support.preludesecurity.com/?hsLang=en)
2. [CLI](https://support.preludesecurity.com/cli?hsLang=en)

# Unable to use CLI after Platform 2.10 upgrade

Prelude made major changes to the platform authentication the week of March 24 2025.  This included the deprecation of legacy token based authentication.  In the weeks before the update, Prelude asked users to upgrade the CLI to migrate the keychain file format prior to the platform upgrade.  In the event a user did not upgrade the CLI prior to the platform upgrade, the user will need to manually update their keychain file.  

The keychain file needs to be updated with the user handle (email address).

 

**Where is my keychain?**

`macOS/Linux - $HOME/.prelude/keychain.ini`

`Windows - %USERPROFILE%\.prelude\keychain.ini`

 

**Original keychain.ini format/contents**

`[myexample]`

`hq = https://api.us1.preludesecurity.com`

`account = aa12345ef5276ccf181b55a5c3c01199`

`token = 12345678-cf00-45e9-a731-cfa70d52bec4`

 

**Updated keychain.ini**

`[myexample]`

`hq = https://api.us1.preludesecurity.com`

`account = aa12345ef5276ccf181b55a5c3c01199`

`handle = someone@preludesecurity.com`

The ini must include the user handle and the token is no longer valid/used and can be removed.  We have also added OIDC support for the CLI, if OIDC is used for the user account (handle) than the INI would look like this:

 

**Updated keychain.ini for OIDC login**

`[myexample]`

`hq = https://api.us1.preludesecurity.com`

`oidc = custom `

`handle = someone@preludesecurity.com`

`account = aa04201ef5276ccf181b55a5c3c01199`

`slug = production-prelude-company`

 

**NOTE:**  The default oidc slug is the account number, if you dont remember your slug you can view it in your Prelude console by navigating to  Settings and "OpenID Connect Settings". 

NOTE: The value for oidc should be "custom" for SSO, "google" for Google social login or not present if not using OIDC, though any other value is considered "not present".

 

- [Monitor](https://support.preludesecurity.com/monitor?hsLang=en#main-content)

    - [Introduction to Control Monitor](https://support.preludesecurity.com/monitor?hsLang=en#introduction-to-control-monitor)
    - [Configuration](https://support.preludesecurity.com/monitor?hsLang=en#configuration)
    - [Client Hardware Security Integrations](https://support.preludesecurity.com/monitor?hsLang=en#client-hardware-security-integrations)
    - [Device Discovery Integrations](https://support.preludesecurity.com/monitor?hsLang=en#device-discovery-integrations)
    - [EDR Integrations](https://support.preludesecurity.com/monitor?hsLang=en#edr-integrations)
    - [Email Integrations](https://support.preludesecurity.com/monitor?hsLang=en#email-integrations)
    - [Identity Management Integrations](https://support.preludesecurity.com/monitor?hsLang=en#identity-management-integrations)
    - [Endpoint Management Integrations](https://support.preludesecurity.com/monitor?hsLang=en#endpoint-management-integrations)
    - [Vulnerability Management Integrations](https://support.preludesecurity.com/monitor?hsLang=en#vulnerability-management-integrations)
    - [Reporting](https://support.preludesecurity.com/monitor?hsLang=en#reporting)
    - [Troubleshooting](https://support.preludesecurity.com/monitor?hsLang=en#troubleshooting)
- [Detect](https://support.preludesecurity.com/detect?hsLang=en#main-content)

    - [Basics](https://support.preludesecurity.com/detect?hsLang=en#basics)
    - [Integrations](https://support.preludesecurity.com/detect?hsLang=en#integrations)
    - [Probe deployment](https://support.preludesecurity.com/detect?hsLang=en#probe-deployment)
    - [Security tests](https://support.preludesecurity.com/detect?hsLang=en#security-tests)
    - [Alert suppression](https://support.preludesecurity.com/detect?hsLang=en#alert-suppression)
    - [Assurance](https://support.preludesecurity.com/detect?hsLang=en#assurance)
- [Integrations](https://support.preludesecurity.com/integrations?hsLang=en#main-content)

    - [SASE](https://support.preludesecurity.com/integrations?hsLang=en#sase)
- [Account](https://support.preludesecurity.com/account?hsLang=en#main-content)

    - [SSO](https://support.preludesecurity.com/account?hsLang=en#sso)
- [CLI](https://support.preludesecurity.com/cli?hsLang=en)
- [Release Notes](https://support.preludesecurity.com/release-notes?hsLang=en)

[![Origin Technology Logo](https://support.preludesecurity.com/hs-fs/hubfs/origin_logo_inverse_000000.png?width=5000&height=5000&name=origin_logo_inverse_000000.png "Origin Technology Logo")](http://originhq.com)

Prelude Security Knowledge Base

Copyright © 2026, Origin Technology