Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Disabling a tenant?

Hi,

I am a Java developer interacting with OpenStack through the REST API - I am unfortunately not yet familiar with the product, but happily learning.

I have a user story by which I need to deactivate a tenant. The business case, I suppose, is pretty standard: if a user happens to not respect my company's conditions of service, then we want to block all accesses to his/her tenant(s), so that no one can access it anymore, in any of read/write mode.

I have checked out the API documentation, and found out that a tenant could be as easily enabled/disabled as setting the "enabled" property of the tenant object, using an updateTenant service call.

<url:http: docs.openstack.org="" api="" openstack-identity-service="" 2.0="" content="" post_updatetenant_v2.0_tenants__tenantid__admin_api_service_developer_operations-d1e1356.html="">

My problem, however, is that the setting of this property, while reported to be working by the code returned by the service call, does not happen to yield the effects that I expect. Namely, even with a disabled tenant, I can still insert some object into a container held by the tenant.

Hence my question: how do I effectively disable/enable a tenant, so as to prevent any write/read on it? Am I using the right method (and if so, why is it failing)? Should I use another approach? Could this possibly be related to some security setting (roles or tokens in use)?

Thank you in advance for your insight.

Kind regards.

Disabling a tenant?How do I effectively disable/enable a tenant using the API?

Hi,

I am a Java developer interacting with OpenStack through the REST API - I am unfortunately not yet familiar with the product, but happily learning.

I have a user story by which I need to deactivate a tenant. The business case, I suppose, is pretty standard: if a user happens to not respect my company's conditions of service, then we want to block all accesses to his/her tenant(s), so that no one can access it anymore, in any of read/write mode.

I have checked out the API documentation, and found out that a tenant could be as easily enabled/disabled as setting the "enabled" property of the tenant object, using an updateTenant service call.

<url:http: docs.openstack.org="" api="" openstack-identity-service="" 2.0="" content="" post_updatetenant_v2.0_tenants__tenantid__admin_api_service_developer_operations-d1e1356.html="">call.

My problem, however, is that the setting of this property, while reported to be working by the code returned by the service call, does not happen to yield the effects that I expect. Namely, even with a disabled tenant, I can still insert some object into a container held by the tenant.

Hence my question: how do I effectively disable/enable a tenant, so as to prevent any write/read on it? Am I using the right method (and if so, why is it failing)? Should I use another approach? Could this possibly be related to some security setting (roles or tokens in use)?

Thank you in advance for your insight.

Kind regards.