OCS provisioning API to enable/disable a user

[PVince81]

Make it possible to change the value of the "enabled" attribute using the provisioning API.

To round up the feature #12601 a bit.

[noveens]

@PVince81 ,
what exactly is the significance of the "enabled" attribute,
and what exactly needs to be solved in this issue?

[DeepDiver1975]

Already existing in oc10 - https://github.com/owncloud/core/blob/master/apps/provisioning_api/appinfo/routes.php#L49-L50

[DeepDiver1975]

9.1 as well - https://github.com/owncloud/core/blob/stable9.1/apps/provisioning_api/appinfo/routes.php#L49-L50

[PVince81]

Ah ok... I tried to PUT the value to the attribute but that didn't work.

[SamuAlfageme]

@PVince81 hmmm...

I tried to PUT the value to the attribute but that didn't work

I just stumbled upon this old https://github.com/owncloud/documentation/issues/2599 issue. And I believe there's some non-deterministic behavior in the OCS APIs related to the use of the OCS-APIREQUEST header in some requests. Might explain what you saw there. Care to do a quick test?

[PVince81]

@SamuAlfageme nothing to do with OCS-APIREQUEST. I simply used the wrong route.

If you do a PUT with the "enabled=true" value the backend just ignores the value.
You need to do a PUT on the "/$userId/enable" endpoint

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.