1
0
mirror of https://github.com/Unleash/unleash.git synced 2024-12-22 19:07:54 +01:00
unleash.unleash/website/docs/reference/api/legacy/unleash/admin/user-admin.md
Thomas Heartman d5fbd0b743
refactor: move docs into new structure / fix links for SEO (#2416)
## What

This (admittedly massive) PR updates the "physical" documentation
structure and fixes url inconsistencies and SEO problems reported by
marketing. The main points are:

- remove or move directories : advanced, user_guide, deploy, api
- move the files contained within to the appropriate one of topics,
how-to, tutorials, or reference
- update internal doc links and product links to the content
- create client-side redirects for all the urls that have changed.

A number of the files have been renamed in small ways to better match
their url and to make them easier to find. Additionally, the top-level
api directory has been moved to /reference/api/legacy/unleash (see the
discussion points section for more on this).

## Why

When moving our doc structure to diataxis a while back, we left the
"physical' files lying where they were, because it didn't matter much to
the new structure. However, that did introduce some inconsistencies with
where you place docs and how we organize them.

There's also the discrepancies in whether urls us underscores or hyphens
(which isn't necessarily the same as their file name), which has been
annoying me for a while, but now has also been raised by marketing as an
issue in terms of SEO.

## Discussion points

The old, hand-written API docs have been moved from /api to
/reference/api/legacy/unleash. There _is_ a /reference/api/unleash
directory, but this is being populated by the OpenAPI plugin, and mixing
those could only cause trouble. However, I'm unsure about putting
/legacy/ in the title, because the API isn't legacy, the docs are. Maybe
we could use another path? Like /old-docs/ or something? I'd appreciate
some input on this.
2022-11-22 09:05:30 +00:00

6.7 KiB

title
/api/admin/user-admin

In order to access the admin API endpoints you need to identify yourself. Unless you're using the none authentication method, you'll need to create an ADMIN token and add an Authorization header using the token.

List all users

GET https://unleash.host.com/api/admin/user-admin

Will return all users and all available root roles for the Unleash instance.

Body

{
  "rootRoles": [
    {
      "description": "Users with the global admin role have superuser access to Unleash and can perform any operation within the unleash platform.",
      "id": 1,
      "name": "Admin",
      "project": null,
      "type": "root"
    },
    {
      "description": "Users with this role have access most features in Unleash, but can not manage users and roles in the global scope. If a user with a global regular role creates a project, they will become a project admin and receive superuser rights within the context of that project.",
      "id": 2,
      "name": "Editor",
      "project": null,
      "type": "root"
    },
    {
      "description": "Users with this role can only read root resources in Unleash. They may be added as collaborator to specific projects.",
      "id": 3,
      "name": "Viewer",
      "project": null,
      "type": "root"
    }
  ],
  "users": [
    {
      "createdAt": "2021-05-14T08:56:34.859Z",
      "email": "random-user@getunleash.ai",
      "id": 3,
      "imageUrl": "https://gravatar.com/avatar/3066e45cf3a09d9a4b51e08a3ac20749?size=42&default=retro",
      "inviteLink": "",
      "isAPI": false,
      "loginAttempts": 0,
      "rootRole": 1,
      "seenAt": null
    },
    {
      "createdAt": "2021-05-14T08:58:07.891Z",
      "email": "random-user2@getunleash.ai",
      "id": 4,
      "imageUrl": "https://gravatar.com/avatar/90047524992cd6ae8f66e249a7630d80?size=42&default=retro",
      "inviteLink": "",
      "isAPI": false,
      "loginAttempts": 0,
      "rootRole": 1,
      "seenAt": null
    }
  ]
}

Get a single users

GET https://unleash.host.com/api/admin/user-admin/:id

Will return a single user by id.

Body

{
  "createdAt": "2021-05-14T08:58:07.891Z",
  "email": "random-user2@getunleash.ai",
  "id": 4,
  "imageUrl": "https://gravatar.com/avatar/90047524992cd6ae8f66e249a7630d80?size=42&default=retro",
  "inviteLink": "",
  "isAPI": false,
  "loginAttempts": 0,
  "rootRole": 1,
  "seenAt": null
}

Search for users

You can also search for users via the search API. It will preform a simple search based on name and email matching the given query. Requires minimum 2 characters.

GET http://localhost:4242/api/admin/user-admin/search?q=iv

Body

[
  {
    "email": "iva2@some-mail.com",
    "id": 19,
    "imageUrl": "https://gravatar.com/avatar/6c795493735ff1864f17d47ec52cf0ec?size=42&default=retro"
  },
  {
    "email": "ivar@another.com",
    "id": 20,
    "imageUrl": "https://gravatar.com/avatar/f4b3e16a54bfbe824eb814479053bf88?size=42&default=retro"
  }
]

Add a new user

POST https://unleash.host.com/api/admin/user-admin

Creates a new user with the given root role.

Payload properties

:::info Requirements

The payload must contain at least one of the name and email properties, though which one is up to you. For the user to be able to log in to the system, the user must have an email.

:::

Property name Required Description Example value(s)
email No The user's email address. Must be provided if username is not provided. "user@getunleash.io"
username No The user's username. Must be provided if email is not provided. "Baz the Beholder"
rootRole Yes The role to assign to the user. Can be either the role's ID or its unique name. 2, "Editor"
sendEmail No Whether to send a welcome email with a login link to the user or not. Defaults to true. false
name No The user's name (not the user's username). "Sam Seawright"

Body

{
  "email": "some-email@getunleash.io",
  "username": "Baz the Beholder",
  "rootRole": "Editor",
  "sendEmail": true
}

Return values:

201: Created

{
  "createdAt": "2021-05-18T10:28:23.067Z",
  "email": "some-email@getunleash.io",
  "emailSent": true,
  "id": 1337,
  "imageUrl": "https://gravatar.com/avatar/222f2ab70c039dda12e3d11acdcebd02?size=42&default=retro",
  "inviteLink": "http://localhost:4242/new-user?token=123",
  "isAPI": false,
  "loginAttempts": 0,
  "name": "Some Name",
  "rootRole": 2,
  "seenAt": null
}

400: Bad request

[
  {
    "msg": "User already exists"
  }
]

400: Bad request

[
  {
    "msg": "You must specify username or email"
  }
]

Update a user

PUT https://unleash.host.com/api/admin/user-admin/:userId

Updates use with new fields

Body

{
  "email": "some-email@getunleash.io",
  "name": "Some Name",
  "rootRole": 2
}

Notes

  • userId is required as a url path parameter.
  • All fields are optional. Only provided fields are updated.
  • Note that earlier versions of Unleash required either name or email to be set.

Delete a user

DELETE https://unleash.host.com/api/admin/user-admin/:userId

Deletes the user with the given userId.

Possible return values:

  • 200: OK - user was deleted
  • 404: NOT FOUND - No user with the provided userId was found

Change password for a user

POST https://unleash.host.com/api/admin/user-admin/:userId/change-password

Body

{
  "password": "k!5As3HquUrQ"
}

Return values:

  • 200 OK: Password was changed.
  • 400 Bad Request: Password was not changed. Unleash requires a strong password.
    • This means
      • minimum 10 characters long
      • contains at least one uppercase letter
      • contains at least one number
      • contains at least one special character (symbol)
  • Please see in the response body on how to improve the password.

Validate password for a user

You can use this endpoint to validate the strength of a given password. Unleash requires a strong password.

  • This means
    • minimum 10 characters long
    • contains at least one uppercase letter
    • contains at least one number
    • contains at least one special character (symbol)

http POST http://localhost:4242/api/admin/user-admin/validate-password

Body

{
  "password": "some-simple"
}
  • 200 OK: Password is strong enough for Unleash.
  • 400 Bad Request: Unleash requires a stronger password. Please see in the response body on how to improve the password.