[Bug]: Login succeeds but logged-in state does not persist.

[quantizoor]

Bug Description

I successfully manage to login as per the log from the cli but when checking my logged-in state with teams status I get that I'm not logged in.

user@ubuntu-8gb-fsn1-1:~$ teams login --device-code
To sign in, use a web browser to open the page https://login.microsoft.com/device and enter the code XXXXXXXX to authenticate.
Logged in as xxx@xxx.com
✔ Sideloading: enabled

Azure CLI: not installed
user@ubuntu-8gb-fsn1-1:~$ teams status
⚠ Not logged in
  Run teams login to authenticate.

Steps to Reproduce

1. npm install -g @microsoft/teams.cli@preview
2. teams login --device-code
3. teams status

Expected Behavior

I expect teams status to say I'm logged in.

Actual Behavior

teams status says I'm not logged in.

SDK Version

3.0.0

Languages Affected

All

Additional Context

No response

[heyitsaamir]

Thanks @quantizoor - when you installed the teams cli, did some post-install scripts run? This can happen if you don't run the required post-install scripts by msal-node and msal-node-extensions.

[quantizoor]

Hello @heyitsaamir. No, no post-install script ran. How should I run them?

Also by running the login in verbose mode I got:

Warning: libsecret not found — token cache will be stored unencrypted.
Install it for secure storage: sudo apt install libsecret-1-dev

Which I did install and it seems to be solving the issue, even if the warning is logged also AFTER I've successfully installed libsecret-1-dev.

The problem I'm encountering now is that it occasionally shows that sideloading is allowed for my account and sometimes it isn't? Is this a propagation issue? I granted access to myself approximately 5 hours ago.

user@ubuntu-8gb-fsn1-1:~$ teams login --device-code -v
Warning: libsecret not found — token cache will be stored unencrypted.
Install it for secure storage: sudo apt install libsecret-1-dev
To sign in, use a web browser to open the page https://login.microsoft.com/device and enter the code XXXXXX to authenticate.
Logged in as xxx@xxx.com
✔ Sideloading: enabled

Azure CLI: not installed
user@ubuntu-8gb-fsn1-1:~$ teams status
Warning: libsecret not found — token cache will be stored unencrypted.
Install it for secure storage: sudo apt install libsecret-1-dev
✔ Logged in as xxx@xxx.com
⚠ Sideloading: not allowed for your account
  Sideloading is enabled for the tenant, but your user policy blocks it.
  Ask your admin to enable it in Teams Admin Center →
  Users → Find the user → Policies → App setup policy → "Upload custom apps"

Azure CLI: not installed
user@ubuntu-8gb-fsn1-1:~$ teams status
Warning: libsecret not found — token cache will be stored unencrypted.
Install it for secure storage: sudo apt install libsecret-1-dev
✔ Logged in as xxx@xxx.com
✔ Sideloading: enabled

Azure CLI: not installed

[quantizoor]

EDIT:

Actually, the scripts did run @heyitsaamir

npm http cache @azure/msal-node@https://registry.npmjs.org/@azure/msal-node/-/msal-node-5.2.3.tgz 0ms (cache hit)
npm http cache strip-ansi@https://registry.npmjs.org/strip-ansi/-/strip-ansi-6.0.1.tgz 0ms (cache hit)
npm warn deprecated prebuild-install@7.1.3: No longer maintained. Please contact the author of the relevant native addon; alternatives are available.
npm info run @azure/msal-node-extensions@5.2.3 install node_modules/@microsoft/teams.cli/node_modules/@azure/msal-node-extensions exit 0

> @azure/msal-node-extensions@5.2.3 install
> exit 0

npm info run @azure/msal-node-extensions@5.2.3 install { code: 0, signal: null }
npm info run @azure/msal-node-runtime@0.20.5 install node_modules/@microsoft/teams.cli/node_modules/@azure/msal-node-runtime node ./copyBinaries.js

> @azure/msal-node-runtime@0.20.5 install
> node ./copyBinaries.js

npm info run @azure/msal-node-runtime@0.20.5 install { code: 0, signal: null }
npm info run keytar@7.9.0 install node_modules/@microsoft/teams.cli/node_modules/keytar prebuild-install || npm run build

> keytar@7.9.0 install
> prebuild-install || npm run build

prebuild-install info begin Prebuild-install version 7.1.3
prebuild-install info looking for local prebuild @ prebuilds/keytar-v7.9.0-napi-v3-linux-x64.tar.gz
(node:45905) [DEP0176] DeprecationWarning: fs.R_OK is deprecated, use fs.constants.R_OK instead
(Use `node --trace-deprecation ...` to show where the warning was created)
prebuild-install info looking for cached prebuild @ /root/.npm/_prebuilds/9f1400-keytar-v7.9.0-napi-v3-linux-x64.tar.gz
prebuild-install info found cached prebuild
prebuild-install info unpacking @ /root/.npm/_prebuilds/9f1400-keytar-v7.9.0-napi-v3-linux-x64.tar.gz
prebuild-install info unpack resolved to /usr/lib/node_modules/@microsoft/teams.cli/node_modules/keytar/build/Release/keytar.node
prebuild-install info install Successfully installed prebuilt binary!
npm info run keytar@7.9.0 install { code: 0, signal: null }

added 122 packages in 6s

33 packages are looking for funding
  run `npm fund` for details
npm verbose cwd /root
npm verbose os Linux 6.8.0-124-generic
npm verbose node v24.16.0
npm verbose npm  v11.13.0
npm verbose exit 0
npm info ok

[heyitsaamir]

The problem I'm encountering now is that it occasionally shows that sideloading is allowed for my account and sometimes it isn't? Is this a propagation issue? I granted access to myself approximately 5 hours ago.

It should be propagation, I think. I've seen it take minutes and sometimes hours.

Try ignoring that for now and installing

[heyitsaamir]

@quantizoor any updates?