JSON unmarshal error: `plugins.enabled` returned as `string` instead of `bool`

[Somfic]

After updating to go-passbolt-cli v0.4.0, any command that requires login fails with a JSON unmarshaling error when fetching server settings.

The CLI fails to parse the server settings response because passbolt.plugins.enabled is returned as a string by the server, but ServerPassboltPluginSettings expects a bool type.

Stacktrace

Error: Logging in: Getting Server Settings: json: cannot unmarshal string into Go struct field ServerPassboltPluginSettings.passbolt.plugins.enabled of type bool

Environment

• go-passbolt-cli version: 0.4.0 (Git SHA v0.4.0)
• OS: NixOS, Linux 6.18.2 x86_64
• Installation method: nixpkgs

Steps to Reproduce

1. Configure passbolt CLI with passbolt configure
2. Run any command that requires authentication, e.g., passbolt list resource

I think the ServerPassboltPluginSettings.Enabled field may need to use a custom JSON unmarshaler that handles both string and bool types, or the struct field type should be changed to accommodate the server's response format..

[speatzle]

Hi, what server version are you testing with?

[Somfic]

I'm not entirely sure, it's not hosted by me and I don't have admin permissions for it. However when I query /settings.json this is the faulty field:

[speatzle]

If you login with the extension there should be a small heart in the bottom right corner. Hovering over it should show the client and server version.

[Somfic]

Ah thanks! We're on 5.8.0 for both server and client

[speatzle]

Looks like this might be a misconfiguration by your server admin.

If i remember correctly the inFormIntegration is a setting for the extension if the autofill menu should appear in the password field of a site.

Your admin might have wrongly quoted false with " in the configuration file.

Can you ask them to check?

[Somfic]

Will have to be after christmas break in a week or two, but will ask!

It think it's a conincidence I updated go-passbolt-cli at the same time my admin updated the passbolt server. This has most likely nothing to do with go-passbolt-cli...

Will leave it up to your discretion if you want to close this issue since this is most likely not a go-passbolt issue

[speatzle]

The old cli version did not need the settings so it never fetched them. But they are required for V5 Resources (Encrypted Metadata) Support. So you could downgrade the cli and see if it works again.