update-user-capabilities
************************


Description
===========

Updates the capabilities of the specified user.


Usage
=====

   oci iam user update-user-capabilities [OPTIONS]


Options
=======


--user-id [text]
----------------

The OCID of the user. [required]


--can-use-console-password [boolean]
------------------------------------

Indicates if the user can log in to the console.


--can-use-api-keys [boolean]
----------------------------

Indicates if the user can use API keys.


--can-use-auth-tokens [boolean]
-------------------------------

Indicates if the user can use SWIFT passwords / auth tokens.


--can-use-smtp-credentials [boolean]
------------------------------------

Indicates if the user can use SMTP passwords.


--can-use-customer-secret-keys [boolean]
----------------------------------------

Indicates if the user can use SigV4 symmetric keys.


--if-match [text]
-----------------

For optimistic concurrency control. In the PUT or DELETE call for a
resource, set the *if-match* parameter to the value of the etag from a
previous GET or POST response for that resource.  The resource will be
updated or deleted only if the etag you provide matches the resource's
current etag value.


--wait-for-state [CREATING|ACTIVE|INACTIVE|DELETING|DELETED]
------------------------------------------------------------

This operation creates, modifies or deletes a resource that has a
defined lifecycle state. Specify this option to perform the action and
then wait until the resource reaches a given lifecycle state.


--max-wait-seconds [integer]
----------------------------

The maximum time to wait for the resource to reach the lifecycle state
defined by --wait-for-state. Defaults to 1200 seconds.


--wait-interval-seconds [integer]
---------------------------------

Check every --wait-interval-seconds to see whether the resource to see
if it has reached the lifecycle state defined by --wait-for-state.
Defaults to 30 seconds.


--from-json [text]
------------------

Provide input to this command as a JSON document from a file.

Options can still be provided on the command line. If an option exists
in both the JSON document and the command line then the command line
specified value will be used


-?, -h, --help
--------------

For detailed help on any of these individual commands, enter <command>
--help.
