Skip to content

Fix: PATs are not restricted in SSO user accounts anymore #2715

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
MuchoLucho merged 2 commits into from
Jan 26, 2026
Merged

Fix: PATs are not restricted in SSO user accounts anymore #2715

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b469617
Fix: PATs are not restricted in SSO user accounts anymore
MuchoLucho Dec 12, 2025
f2c2894
feat (personal access token): adds disclaimer identity providers don'…
MuchoLucho Jan 23, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions 10.Server-integration/01.Using-the-apis/docs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -131,12 +131,11 @@ curl -H "Authorization: Bearer $JWT" -X DELETE -k $MENDER_SERVER_URI/api/managem
!! change. This is because the token contains information about your current plan,
!! and it will become invalid upon upgrade.

!! WARNING: Personal access tokens are not automatically revoked for users who are disabled in an identity provider. If using single sign on, users personal access tokens must be revoked separately.

### Session Token

If you are using SSO then Personal Access Tokens are not an option to you.
As such, you can still access the APIs and use mender-cli using a Session Token.
To get the session token navigate to [your profile](https://hosted.mender.io/ui/settings/my-profile) and under "Session token" click "COPY TO CLIPBOARD".
Then use this token anywhere that the Personal Access Token should be used.

Session Tokens have the same validity span as a JWT generated using the login endpoint:
* With "Keep me signed in" they are valid for 24 hours
Expand Down