Basic authentication

overview basic authentication is a simple yet widely used method for authenticating users in web applications and apis it involves sending a username and password in the http header of a request to access protected resources this documentation page provides an overview of basic authentication the users page within the kubeark platform offers users a comprehensive set of metrics and tools to aid in the tracking and management of their users this feature enables users to easily access and modify a variety of user attributes, including attribute description username the login identifier for the user within the kubeark platform name the full name of the user, including both first and last name e mail the user's email address user role the role assigned to the user created the date and time the user account was created status the status of the user account, whether it is active or disabled an active user has the ability to access the platform, while a disabled user has had their access revoked > enabled the user is ready to be used > disabled the user is deactivated and all the roles and permissions are disabled actions the ability to modify or delete the user account, if the user has the necessary permissions level creating a new user to create a new user through kubeark identity, please follow these steps step 1 on the main kubeark page, go to user management and select users from the users page, on the top left corner of the workspace, select idp step 2 this will take you to the user interface of the identity management console from the top right corner of the screen, select admin interface the kubeark identity console presents two different views, which are determined by the role of the user who is accessing them user interface this is the default screen for user accounts admin interface this is the identity management console dedicated to organization admins step 3 within the admin interface go to directory > users on the users page select create step 4 to create a new user in the admin interface , it is necessary to provide specific attributes, as follows attribute description username the unique identifier for the user path the path to the user's location within the system hierarchy name the user's display name, which is visible to other users email the user's email address, which can be used for communication and account recovery groups the groups to which the user should belong, which control access to resources attributes custom attributes that can be defined for the user, using yaml or json these can include additional information about the user, such as job title or department once all of the required attributes are provided, the user can be created by clicking on the create button the new user will be added to the platform and can then be managed and assigned roles, clusters, and permissions as needed