Assigning licence to user accounts v15.16

[vmanera]

Hey y'all,
As per the docs, licences cannot be added to legacy users following a FB upgrade. Documentation mentions an endpoint that licence can be added/removed:

PUT /manage-licenses/v1/licenses/{license-id}/users/{user-id}   Grant a user access to a license.
DELETE /manage-licenses/v1/licenses/{license-id}/users/{user-id} Revoke a users' access to a license.

https://docs.funnelback.com/administer/reference-documents/license_management.html#assigning-a-license-to-a-user

I could not get these to work (got 405 return), however I noticed that each user has a reference to their licences in their account config file:

/opt/funnelback/admin/users/{userId}.ini
[user-info]
licenses={licenceId}

Is this the only place that the API endpoint changes config for this user or does it do more things than this. What exactly does accessing this endpoint touch in the server to make these changes to the user account?

[LukeButters]

Hi,

Does the API respond with anything other than the 405?
Would you mind looking at the logs $SEARCH_HOME/web/log/admin-api.log
Before you tinker directly with the users make sure you upgrade them if the users have been copied from else where (could you tell me if this is the case?). To upgrade run
$SEARCH_HOME/bin/setup/update-configs.pl $SEARCH_HOME/admin/users/
(If you edit them via the UI I think the upgrade is done automatically).
After that you should find the [user-info] section is renamed to [user-details] under that you could put:
license=*
If you just want to let that user have access to all installed licenses otherwise list the specific license IDs.

[vmanera]

I'll admit that after editing the {user}.ini file directly the client was able to see the licence in the UI, so i'm hesitant to touch this any further in case I accidentally break their account access.

In regards to their account: this happened following a funnelback upgrade so from 15.6 => 15.16. I can't speak for the specifics of how the accounts were migrated across as I was not part of that process but I presume it's part of the normal upgrade process.

In any case this should be resolved as client can access their licence.