Request for interface **password-manager-service** auto connect for smart-sip-phone-pro

store-requests privileged-interfaces
1

Hello review team,

we implemented a contact import for CardDAV sources using vdirsyncer and keyring python executables. Our keyring executable needs the password-manager-service interface to be able to set passwords to the OS keychain. Vdirsyncer then uses keyring to read the saved passwords from the keychain.

  • name: smart-sip-phone-pro

  • description: SIP client for every SIP telephone system

  • upstream: PRIVATE

  • upstream-relation: we are the developers and maintainers of the client

  • interfaces:

    • password-manager-service:

      • request-type: auto-connection

      • reasoning: we have implemented a contact integration for CardDAV sources using vdirsyncer and keyring. To save and read passwords from the OS keychain, keyring needs the password-manager-service interface connected.

Kind regards,

Max from EDNT

2

This request has been added to the queue for review by the @reviewers team.

3

Hey @ednt

password-manager-service interface grants the application access to all secrets stored in the keyring. Thus, it is granted only under extremely rare circumstances.

If your application does not need to access secrets not created by itself, you should use the secret-portal instead.

4

Hey @jslarraz ,

that makes sense, especially why password-manager-service is rarely auto-connected.

As we understand it, switching to the Secret Portal would require us to actively use the Desktop Portal API . Since our CardDAV import is based on the Python libs vdirsyncer and keyring, this would likely require a more substantial refactor rather than being a drop-in replacement.

Given that, we’ll stick with our current approach for now and look into smaller workarounds in the short term, while keeping the portal approach in mind for the future.

Thanks again for your reply and suggestion!