-
Notifications
You must be signed in to change notification settings - Fork 17
Closed
Labels
nethlinkThe issue is related to NethLink (NethVoice Desktop client)The issue is related to NethLink (NethVoice Desktop client)nethvoiceBug or features releted to the NethVoice projectBug or features releted to the NethVoice projectnethvoice-ctiThe issue is related to NethLink (NethVoice Web client)The issue is related to NethLink (NethVoice Web client)
Milestone
Description
Problem
The Phone Island API key storage does not support different client types (web vs nethlink), causing session conflicts when users authenticate from multiple clients.
Steps to reproduce
- Login to nethvoice-cti web interface and generate new integration token (under Settings->Integrations)
- Use it in a external application and try to make a call (you can clone phone-island project and run
npm run devthen use the integration token) - Login to nethlink desktop application
- Go back in the external application and the authentication fails with
wrong tokenerror
Root cause
The middleware stores only one phone_island_api_key.json file per user, without distinguishing between client subtypes. Each new login overwrites the previous token, invalidating the other client's session.
Component
nethcti-middleware
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
nethlinkThe issue is related to NethLink (NethVoice Desktop client)The issue is related to NethLink (NethVoice Desktop client)nethvoiceBug or features releted to the NethVoice projectBug or features releted to the NethVoice projectnethvoice-ctiThe issue is related to NethLink (NethVoice Web client)The issue is related to NethLink (NethVoice Web client)
Type
Projects
Status
Done