I cloned a workspace in perforce from other credentials (as i was having some issue with my account back then due to permissions). Now i have the relevant permissions so want to change the owner of that workspace.
In p4v tool, I logged in from the account through which the workspace was created and i tried to change the owner in the advanced options but it gives an error "Client specification failed: You can't create another user's workspace."
Any ideas on how can we change the owner ?
I'd recommend using the command line as it's much faster
p4 client <workspace name>
Then change the Owner: to the one you want, save and you're done.
Related
When I joined my current company, a new user was created for me that had a random capitalized letter in the email address.
All attempts to fix the error were in vain, as there always remained some random place where the capitalization error showed up again.
In the end, IT decided the best solution was to just delete the user and start over (not a big deal as I was a new user).
So far, everything looked OK, until we noticed that in the Azure DevOps (TFS) the old user still showed up in search results, probably since it was not removed before the user was deleted.
As you can see, instead of an e-mail it shows the follwing:
OIDCONFLICT_UpnReuse_3f39b....
Is there a way to delete the old user permanently and prevent it from showing up?
Currently people can tag the old user, which is a big nuisance.
I'm not the IT guy, but I hope to find a lead to help them solve this issue.
Thanks!
You can delete the User permanently by using the below commands in Azure CLI
Note: the below mentioned command require admin access.
az devops user remove --user
--org
--yes
The above mentioned CLI command will help you in removing user permanently from the Azure Devops organization.
Example:
After user put email address
in the link put your organization name
Parameters
user: User's email to be removed.
org: Organization name from which user should be removed.
Below command will help you in configuring default organization if you are not configured
az devops configure -d organization=ORG_URL.
Use the below command if the default organization is picked up from different path
git config.
yes: Don't prompt for confirmation.
you can Refer for further details.
Sign in with a member user from Azure AD into the Azure DevOps organization and go to or click on "Settings / Azure Active Directory"
At the top, you will see a banner with the following message
4 member(s) of the x-ops organization can't sign in because they're not in the XOPSX Azure Active Directory. Delete any unwanted users in Organization settings, and then Resolve for remaining members. with a Resolve button next to it
You will have to click on Resolve to map the "Current Email" with the "Matched Identity in Directory" to map the user with its identity and resolve this issue.
Another project that was created directly in the organization shows me as owner.
Is there a way to fix this in the settings?
I checked the settings/members page, and the only way I see is to click the "Leave" button next to my maintainer status, and then hope that I will automatically be marked as the owner.
The short answer is yes, that's safe to do.
When you transfer a project, all roles are kept "as is". Since by default, you're a Maintainer on the personal project, when you transfer it, it keeps that role for you.
When you have a role in the group, it will inherit the role, unless a role is specified for the project. By deleting your role at the project level, you're just deleting the specified project-specific role. Once you do, you should show up as an Owner (inheriting it from the group).
We have an issue. User is in the Contributors group of the VSTS project. Able to view dashboard and work items. Unable to view Repos. Need help. Any suggestions?
User needed an MSDN license to use Visual Studio in addition to being in the correct group of the VSTS project. Trial license was not good enough.
According to your description, highly doubt those users only have Stakeholder access level.
People with Stakeholder access level could not commit their work on branch and unable to view repos.
Assign Stakeholder access to those users who need to enter bugs,
view backlogs, boards, charts, and dashboards, but who don't buy basic access. Stakeholders can also view releases and manage release
approvals. Stakeholder access is free.
Source Link: About access levels
See Stakeholder access for details of features available to stakeholders.
The user should have either Basic access or Visual Studio subscription which include code feature.
Moreover, if it's still not able to see any other projects after giving them those access. There is another concept called Permissions in Azure DevOps. Double check the permission for Contributor group.
Also make sure you have not add them to any other project team group expect the contribute group.
Once deny the Read permission for repos level, user will not be able to see the repos.
Read
Can read the contents of a file or folder. If a user has Read
permissions for a folder, the user can see the contents of the folder
and the properties of the files in it, even if the user does not have
permission to open the files.
I created a user account on Amazon Linux Instance with root user. I found that if I create a user account(Example: ec2-user) that account will not have execute and write permissions on Hadoop Files System, Hive, Pig and other tools which are installed on Amazon EMR. If I have to give them explicit permissions I have to create a group which has permissions equivalent to superuser(root) account and add users to that group. Is there any other way I can set up access for those accounts to HDFS, Hive and Pigs etc.
Also while logging in as user the Linux command prompt is not prompting to enter any password even though I gave password for the user account while creating it. Is there anything configuration changes I need to make in /etc/ssh/sshd_config file?
Your question is not that clear to me.
But, let me attempt with whatever I suppose I understood.
Hadoop when security is enabled needs to have security for each user. It seems your user needs a separate space for writes and executions i.e. a Home directory.
First login as 'hdfs' user in a terminal and then create a home directory for your user in HDFS. Please check if you have a directory called /user/{yourUser}. If, not create that. Then, make sure you make {yourUser} the owner of /user/{yourUser}.
I want to update my own comment for a commit in the check-in history but I receive error as snapshot as below.
I understand that my account is not an admin/owner of the repository but it should be allowed me to update my own comment! On TFS side, I can do this actually.
Is there any work-around for me? I don't want to provide admin right to all users.
You don't have to give every user admin rights. But the error returned by your pre-revprop-change hook script tells you that only admins or project owners can change log messages.
So either change your pre-revprop-change hook script to allow all users to do that, or add yourself to the owners group or admin group.