DOC-5748 DOC-5779 Added last_login to user REST API reference and changes related to blocking new user creation after the maximum limit is reached

Author: rrelledge

content/embeds/rs-prometheus-metrics-v2.md

@@ -78,6 +78,7 @@
 | <span class="break-all">total_node_count{cluster_wd=<node_uid>}</span> | gauge| Number of nodes |
 | <span class="break-all">total_primary_selection_ended{cluster_wd=<node_uid>}</span> | counter | Monotonic counter for each selection process that ended |
 | <span class="break-all">total_primary_selections{cluster_wd=<node_uid>}</span> | counter | Monotonic counter for each selection process that started|
+| users_count | gauge | Current number of users on the cluster |
 
 ## Replication metrics
 

content/operate/rs/references/rest-api/objects/cluster/alert_settings.md

@@ -29,6 +29,7 @@ weight: $weight
 | cluster_ocsp_status_revoked | boolean (default: false) | OCSP certificate status is REVOKED |
 | cluster_ram_overcommit | boolean (default: false) | RAM committed to databases is larger than cluster total RAM |
 | cluster_too_few_nodes_for_replication | boolean (default: false) | Replication requires at least 2 nodes in the cluster |
+| cluster_users_count_approaches_limit | <span class="break-all">[cluster_alert_settings_with_threshold]({{< relref "/operate/rs/references/rest-api/objects/cluster/cluster_alert_settings_with_threshold" >}})</span> object | Number of users approaches the maximum limit of 32,000 users. This alert is enabled with a 90% threshold by default on new clusters. |
 | node_aof_slow_disk_io | boolean (default: false) | AOF reaching disk I/O limits
 | node_checks_error | boolean (default: false) | Some node checks have failed |
 | node_cpu_utilization | <span class="break-all">[cluster_alert_settings_with_threshold]({{< relref "/operate/rs/references/rest-api/objects/cluster/cluster_alert_settings_with_threshold" >}})</span> object | Node CPU utilization has reached the threshold value (% of the utilization limit) |

content/operate/rs/references/rest-api/objects/user.md

@@ -14,17 +14,18 @@ weight: $weight
 |------|------------|-------------|
 | uid | integer | User's unique ID |
 | account_id | integer | SM account ID |
-| action_uid | string | Action UID. If it exists, progress can be tracked by the `GET` `/actions/{uid}` API request (read-only) |
+| action_uid | string | Action UID. If it exists, progress can be tracked by the <span class="break-all">`GET /actions/{uid}`</span> API request (read-only) |
 | auth_method | **'regular'**<br />'certificate'<br />'entraid' | User's authentication method |
 | bdbs_email_alerts | complex object | UIDs of databases that user will receive alerts for |
-| certificate_subject_line | string | The certificate’s subject line as defined by RFC2253. Used for certificate-based authentication users only. |
+| <span class="break-all">certificate_subject_line</span> | string | The certificate’s subject line as defined by RFC2253. Used for certificate-based authentication users only. |
 | cluster_email_alerts | boolean | Activate cluster email alerts for a user |
 | email | string | User's email (pattern matching only ASCII characters) |
-| email_alerts | boolean (default:&nbsp;true) | Activate email alerts for a user |
+| email_alerts | boolean (default: true) | Activate email alerts for a user |
+| last_login | integer | UNIX timestamp of the user's last login time. This denotes the last time an authentication with the user's credentials was successful. (read-only) |
 | name | string | User's name (pattern does not allow non-ASCII and special characters &,\<,>,") |
-| password | string | User's password. If `password_hash_method` is set to `1`, the password should be hashed using SHA-256. The format before hashing is `username:clustername:password`. | 
-| password_hash_method | '1' | Used when password is passed pre-hashed to specify the hashing method |
-| password_issue_date | string | The date in which the password was set (read-only) |
+| password | string | User's password. If `password_hash_method` is set to `1`, the password should be hashed using SHA-256. The format before hashing is <span class="break-all">`username:clustername:password`</span>. | 
+| <span class="break-all">password_hash_method</span> | '1' | Used when password is passed pre-hashed to specify the hashing method |
+| <span class="break-all">password_issue_date</span> | string | The date in which the password was set (read-only) |
 | role | 'admin'<br />'cluster_member'<br />'cluster_viewer'<br />'db_member'<br /> **'db_viewer'** <br />'user_manager'<br />'none' | User's [role]({{< relref "/operate/rs/references/rest-api/permissions#roles" >}}) |
 | role_uids | array of integers | UIDs of user's roles for role-based access control |
 | status | 'active'<br />'locked'<br />'password_expired' | User sign-in status (read-only)<br />**active**: able to sign in<br />**locked**: unable to sign in<br />**password_expired**: unable to sign in because the password expired |

content/operate/rs/release-notes/rs-8-0-releases/rs-8-0-tba.md

@@ -133,6 +133,12 @@ The [metrics stream engine]({{<relref "/operate/rs/monitoring/metrics_stream_eng
         crdb-cli crdb update --crdb-guid <guid> --update-db-config-modules true
         ```
 
+- Added a check to block new user creation after the maximum limit of 32,000 users has been reached:
+
+    - Added a [cluster alert]({{<relref "operate/rs/references/rest-api/objects/cluster/alert_settings">}}) `cluster_users_count_approaches_limit`, which triggers when the number of users surpasses a threshold percentage of the maximum user limit. This alert is enabled with a 90% threshold by default on new clusters.
+
+    - Added a `users_count` cluster metric to [Prometheus metrics v2]({{<relref "/operate/rs/references/metrics/prometheus-metrics-v2">}}) that shows the current number of users on the cluster.
+
 - New [database configuration]({{<relref "/operate/rs/references/rest-api/requests/bdbs">}}) fields in the REST API for automatic shard balancing:
 
     - `auto_shards_balancing`: Automatically balances database shards.
@@ -145,6 +151,8 @@ The [metrics stream engine]({{<relref "/operate/rs/monitoring/metrics_stream_eng
 
 - Additional REST API enhancements:
 
+    - New `last_login` field for [users]({{<relref "/operate/rs/references/rest-api/requests/users">}}), which stores the UNIX timestamp of the user's last successful login to the Cluster Manager UI or REST API.
+
     - Added [cluster configuration]({{<relref "/operate/rs/references/rest-api/requests/cluster">}}) fields:
 
         - `disconnect_clients_on_password_removal`: Controls whether client connections using removed, revoked, or rotated passwords are actively disconnected.