I've installed devstack to a clean Ubuntu machine. I'm able to access the OpenStack Dashboard at http://localhost/auth/login/. However, I have no idea how to manage users or what my initial credentials are.
Where is this information is kept?
The information is kept in the Keystone MySQL database. Do not edit the DB directly!
You'll want to manage users via the Keystone CLI. To do this you need to source your DevStack admin creds properly.
cd devstack
source openrc admin admin
echo $OS_USERNAME
echo $OS_TENANT_NAME
echo $OS_PASSWORD
I put the echo commands there to show you how to discover your creds.
To use the Keystone CLI checkout the docs Creating Tenants, Users, Roles, Tokens and Endpoints and Manage projects, users, and roles.
If you want to work with the CLIs as a non-admin user just do
cd devstack
source openrc
echo $OS_USERNAME
echo $OS_TENANT_NAME
echo $OS_PASSWORD
Related
The functions described in the following article do not exist in any of the powershell packages that I can find for Teams/Skype.
https://learn.microsoft.com/en-us/graph/cloud-communication-online-meeting-application-access-policy
New-CsApplicationAccessPolicy
Grant-CsApplicationAccessPolicy
Looking for a way to Allow applications to access online meetings on behalf of a user - anyone have suggestions here?
It won't be any part of existing package of your powershell installation. You need an administrator or owner level user of your subscription to import it.
Have your admin user follow the below steps:
Open Powershell in admin mode
type Install-Module MicrosoftTeams
type Y
type Set-ExecutionPolicy -ExecutionPolicy AllSigned -Scope CurrentUser
type
Import-Module MicrosoftTeams
$sfbSession = New-CsOnlineSession
Import-PSSession $sfbSession
After that, your admin person can run the New-CsApplicationAccessPolicy and Grant-CsApplicationAccessPolicy for you.
I am using airflow (1.8.0) and using web UI I can create a user but it doesn't allow me to set a password. But is it possible via command line to
create new user with password
assign role/permissions to a user
how to limit and manage access of user/group so that they cannot change or trigger someone else's DAG
I have seen apache-airflow (1.10.0) which does have cli feature to create a user with password (https://airflow.apache.org/cli.html#create_user), but cannot see anything around setting access level and permissions.
Airflow 1.8.0 doesn't support CLI password creation.
You can create user and set a password as it is described here.
Airflow 1.10.0 doesn't allow to manage permissions for a given user, future releases should have this feature.
Recently I installed the Bitnami Wordpress canned deployment on Google Cloud Platform.
I can view the phpMyAdmin instance at a local address (http://127.0.0.1:8888/phpmyadmin/) but I cannot determine the username and password to log into the database cluster. I have tried the username specified in Deployment Manager, but the temporary password is not working. When I attempt to login, I receive the following error:
mysqli_real_connect(): (HY000/1045): Access denied for user 'user'#'localhost' (using password: YES)
I have tried to use various common passwords, such as root/root, with no success. If we assume the password is lost, how I can I figure out the password, recover it, or change it by using an SSH shell to the hosting compute instance?
Resetting password by supporting team if possible try
This issue seems related to phpmyadmin. I found this similar post where they stated:
This is asking for your MySQL username and password.
You should enter these details, which will default to "root" and ""
(i.e.: nothing) if you've not specified a password.
UPDATE
Have you tried to create a new user or change the password? Check this guide on how to do it.
Bitnami Engineer here,
As our guide mentions, once you create the SSH tunnel to access phpMyAdmin, you need to use the user 'root' and the password we configure at boot time (it's the same password we configure in the application). More information in our documentation
https://docs.bitnami.com/google/components/phpmyadmin/
Oh it's opened now, the user was (root) which it's not mentioned anywhere when i created the instance, the password is the one which generated by Bitnami when the instance is created on the bitnami platform lunchpad website.
the password is used for 2 users :
username: user
username : root (hidden) for new users who are decided to try cloud servers is not easy to figure this username and which password must use.
thanks for trying to help.
I created a VM instance on gcloud hosting Rstudio. However, after a month of not using the server I forgot the password of the VM instance and not sure if I'm using the right user name. When I tried to login by external IP:8787 the credentials that I remember are not valid. Does anyone know how to recover password and username for VM instance?
Thank you!
You should connect to your rstudio Vm via SSH and then you will be able to choose new password by following these steps:
Go to your VM instances page and in the list of virtual machine instances, click SSH in the row of the instance that you want to connect to.
When you log-in your VM via SSH:
1) Run the command sudo passwd < YOUR_USERNAME > (Keep in mind by default the admin username is rstudio-user) .
2) Type the new password and then retype it and done.
3) Try to connect to your VM with your new password
Moreover, if you are not using the default username or you forget, you can run
sudo cat /etc/passwd to see the username when you logged in to your VM via SSH.
To switch to an admin user(root) in unix I use :
sudo su -
so now I'm an admin user with admin privilages. To achieve same in windows I would need to login with an admin password before becomming an admin.
Why is this different in unix ? I'm a unix newbie so maybe there is something more going on that I am not aware of ?
I will use admin and root interchangeable for explaining the following:
When you use sudo su, you are basically saying "use my permission in the sudoers file and log me in to the root user."
When you use sudo, you are basically saying "use my permission for current user (who is in sudoers file) and execute the following command which comes after sudo."
Sudoers file is a file that defines the permission for various users in UNIX and Linux and whether or not they can run commands as sudo (super user do).
When you use su, you are saying "start a new session and log me in as root directly, without checking sudoers files, and I will provide the credentials (password)."
The difference in UNIX is the management of the admin account. Root exists for the entire system. All users are allowed to log into root if they provide the correct credentials. For all accounts, any user can run things as though the user is root (su) by adding the particular user account to the sudoers file. This means that any user account can execute sudo commands as if it was an admin account by only providing the user's password. And the user does not have to know the root password. It basically says: "I know what I am doing, let me do it." And it means that a user can execute as both a regular user and admin in one session, without having to log in and log out of accounts.
While in Windows, the admin management is handled differently. A sudoer file does not exist in Windows. A user is either administrator or not. However, if the user is administrator, he can still run things as a normal user without going to OS permissions right-clicking an doing Run as administrator. Also, there is no overall root account for Windows unless it was set by whoever set up the system.
The way admin privileges are managed is different, nothing else.
Hmm... I'm not sure I'm understanding your question, but here is my answer:
When you write sudo su - (or sudo -s), you'll be asked your current user password. If that user doesn't have the privileges to perform sudo tasks, you won't be able to do that.
You're saying:
...I would need to login with an admin password before becomming an admin.
As I said, your user is kind of an admin one, because someone gave you that privilege (either by adding you to the sudoers file, adding you to the adm group, etc).
if you want to be root on unix and have the root password you can do
su - which is the same as su - root.
Back in the day you had the option to login as root aka admin but that has gone away due to security reasons. Now you are required to login as yourself and then become root.
In the windows world this is the same as logging in as a non-privledged user and running a program as administrator. When you do this in windows you will also be prompted for the admin password. Basicly the same thing in unix.
The reason for the sudo is because most places dont want a user to have the root password.
sudo su - will prompt you for your personal unix password not root's. And then check the sudoconfig to make sure you are allowed to run that command.
sudo also has the abilty to give a user very restricted access. It can be set up so only certain users or groups can run specfic commands as root or other users.
In addtional to making sure you are allowed to run the command it will also keep a log as to who ran what. Or if someone is trying to become root who is not allowed.