Eduard Kabrinskiy - Azure devops pat - Кабринский Рдуард
Azure devops pat
Azure devops pat News sites Azure devops pat
Use personal access tokens
Azure DevOps Services | Azure DevOps Server 2020 | Azure DevOps Server 2019 | TFS 2018 - TFS 2017
A personal access token (PAT) is used as an alternate password to authenticate into Azure DevOps. Learn how to create, use, modify, and revoke PATs for Azure DevOps.
If you're working within Microsoft tools, then your Microsoft account (MSA) or Azure Active Directory (Azure AD) is an acceptable and well-supported approach. But, if you're working with 3rd party tools that don't support Microsoft or Azure AD accounts – or you don't want to provide your primary credentials to the tool – you can make use of PATs to limit your risk.
PATs are easy to create when you need them and easy to revoke when you donРІР‚в„ўt. To set up PATs for non-Microsoft tools, use Git credential managers or create them manually. We recommend that you review our authentication guidance to help you choose the correct authentication mechanism. For smaller projects that require a less robust solution, PATs are a simple alternative. Unless your users are using a credential manager, they have to enter their credentials each time.
Create a PAT
To enable the new user interface for the New account manager page, see Manage or enable features.
Sign in to your organization in Azure DevOps ( https://dev.azure.com/ )
From your home page, open your user settings, and then select Personal access tokens.
And then select + New Token.
Name your token, select the organization where you want to use the token, and then choose a lifespan for your token.
Select the scopes for this token to authorize for your specific tasks.
For example, to create a token to enable a build and release agent to authenticate to Azure DevOps Services, limit your token's scope to Agent Pools (Read & manage). To read audit log events, and manage and delete streams, select Read Audit Log, and then select Create.
When you're done, make sure to copy the token. For your security, it won't be shown again. Use this token as your password.
Sign in to your organization in Azure DevOps ( https://dev.azure.com/ )
From your home page, open your profile. Go to your security details.
Select + New Token.
Name your token, select the organization where you want to use the token, and then choose a lifespan for your token.
Select the scopes for this token to authorize for your specific tasks.
For example, to create a token to enable a build and release agent to authenticate to Azure DevOps Services, limit your token's scope to Agent Pools (Read & manage), and then select Create.
When you're done, make sure to copy the token. For your security, it won't be shown again. Use this token as your password.
Sign in to your web portal ( https://:8080/tfs/ ).
From your home page, open your profile. Go to your security details.
Create a personal access token.
Name your token. Select a lifespan for your token.
If you have more than one organization, you can also select the organization where you want to use the token.
Select the scopes for this token to authorize for your specific tasks.
For example, to create a token to enable a build and release agent to authenticate, limit your token's scope to Agent Pools (read, manage).
When you're done, make sure to copy the token. For your security, it won't be shown again. Use this token as your password. Select Close.
Once your PAT is created, you can use it anywhere your user credentials are required for authentication in Azure DevOps.
Notifications
Users receive two notifications during the lifetime of a PAT - one upon creation and the other seven days before the expiration.
After you create a PAT, you receive a notification similar to the following example.
Seven days before your PAT expires, you receive a notification similar to the following example.
Unexpected notification
If you receive an unexpected PAT notification, an administrator or tool might have created a PAT on your behalf. See the following examples.
When you connect to an Azure DevOps Git repo through git.exe. it creates a token with a display name like "git: https://MyOrganization.visualstudio.com/ on MyMachine."
When you or an administrator sets up an Azure App Service web app deployment, it creates a token with a display name like "Service Hooks: : Azure App Service: : Deploy web app."
When you or an administrator sets up web load testing, as part of a pipeline, it creates a token with a display name like "WebAppLoadTestCDIntToken".
When a Microsoft Teams Integration Messaging Extension is set up, it creates a token with a display name like "Microsoft Teams Integration".
If you believe that a PAT exists in error, we suggest that you revoke the PAT. Then, change your password. As an Azure AD user, check with your administrator to see if your organization was used from an unknown source or location.
Use a PAT
Your token is your identity and represents you when it's used. Treat and use a PAT like your password.
Git interactions require a username, which can be anything except the empty string. The PAT is used as the password. Additionally, you have to Base64-encode the username and PAT to use it with HTTP basic authentication. On Linux or macOS, in Bash, you can enter:
On Windows, you can do something similar in PowerShell:
To keep your token more secure, use credential managers so you don't have to enter your credentials every time. We recommend the following credential manager:
Use a PAT in your code
See the following sample that gets a list of builds using curl.
If you wish to provide the PAT through an HTTP header, first convert it to a Base64 string (the following example shows how to convert to Base64 using C#). The resulting string can then be provided as an HTTP header in the following format: Authorization: Basic BASE64_USERNAME_PAT_STRING Here it is in C# using the HttpClient class.
When you're using variables, add a "$" at the beginning of the string, like in the following example.
When your code is working, it's a good time to switch from basic auth to OAuth.
If you enable IIS Basic Authentication for TFS, PATs aren't valid. For more information, see Using IIS Basic Authentication with TFS on-premises.
Modify a PAT
You can regenerate or extend a PAT, and modify its scope.
To enable the new user interface for the New account manager page, see Manage or enable features.
From your home page, open your user settings, and then select Profile.
Under Security, select Personal access tokens. Select the token for which you want to modify, and then select Edit.
Edit the token name, organization it applies to, token expiration, or the scope of access that's associated with the token, and then select Save.
From your home page, open your profile. Go to Security details.
Select the token for which you want to modify, and then select Edit.
Edit the token name, organization it applies to, token expiration, or the scope of access that's associated with the token, and then select Save.
Revoke a PAT
You can revoke a PAT at any time, for various reasons.
To enable the new user interface for the New account manager page, see Manage or enable features.
From your home page, open your user settings, and then select Profile.
Under Security, select Personal access tokens. Select the token for which you want to revoke access, and then select Revoke.
Select Revoke in the confirmation dialog.
From your home page, open your profile. Go to Security details.
Select the token for which you want to revoke access, and then select Revoke.
Select Revoke in the confirmation dialog.
Related articles
Q: Is there a way to renew a PAT via REST API?
A: No, we don't have a REST API to renew a PAT. You can only regenerate a PAT within the user interface (UI).
Q: Can I use basic auth with all of Azure DevOps REST APIs?
A: No. You can use basic auth with most of them, but organizations and profiles only support OAuth.
Azure devops pat
Azure devops pat
Azure devops pat New Azure devops pat
Azure devops pat
Use personal access tokens (PATs) as alternate passwords to authenticate access to Azure DevOps.
Azure devops pat
Azure devops pat Azure devops pat Azure devops pat
SOURCE: Azure devops pat Azure devops pat Azure devops pat
#tags# -,-Azure devops pat] Azure devops pat#tags#
Кабринский Эдуард
news today |
Датчик расхода ДРС предназначен для измерения нефти, нефтепродуктов, воды, их смесей, сжиженных газов и других жидкостей в технологических процессах нефтедобывающей, нефтеперерабатывающей отраслей, а также на предприятиях общепромышленного назначения и в коммунальном хозяйстве.
Датчик расхода ДРС, предназначен для линейного преобразования объёмного расхода жидкости, протекающей в трубопроводе, в последовательность электрических импульсов с нормированной ценой в зависимости от типоразмера датчика расхода, в токовый сигнал 4-20 мА, интерфейс HART и Modbus.
Датчик расхода может эксплуатироваться в составе счётчика жидкости СЖУ, счетчика тепловой энергии СТС.М или в составе других изделий и информационно-измерительных систем, воспринимающих электрические импульсные сигналы, с частотой в диапазоне 0,2–250 Гц или токовые сигналы.
По желанию заказчика, датчик расхода жидкости ДРС, может быть оснащен визуализацией измеряемых параметров (расход, время наработки, диагностика) на встроенном мониторе.
По специальному заказу может быть изготовлен «газоустойчивый» вариант датчика расхода ДРС-..Г , для сред содержащих газовую фазу до 5%.
Подробнее: https://neftel.ru/datchik-rashoda-zhidkosti-tipa-drs |
Эдуард Кабринский - Chef and puppet - Рдуард Кабринский
Chef and puppet
Chef and puppet Latest breaking news Chef and puppet
Ansible vs Chef vs Puppet
The configuration Management system is all about deploying the application into servers, Managing Servers and Configuring Servers. The most common and popular configuration tools available in the market are Ansible, Chef, and Puppet. In this article, we will see these tools and discuss the pros and cons of Ansible vs Chef vs Puppet so that we can choose the right configuration management tools for our need.
Table of Contents
Ansible
Ansible is the youngest among the other configuration management tools. The basic platform of the Ansible is written in python and the basic scripting can be written in YAML. Ansible is PUSH based configuration management tool which means it will send the configuration from workstation to the nodes using SSH or winRM connection. Let us see the simple architectural diagram of the ansible to understand working method.
Ansible needs a workstation where ansible scripts will get executed. So Ansible scripts will look for the inventory files which are having the list of hostnames or IP addresses of the target servers.
Roles and modules are the single or list of components and commands that need to be configured in the target system. When the Ansible script is executed, it will establish the SSH or WinRM connection with the target servers as per the inventory file and execute the roles and modules on the target servers. Let us see the Pros and Cons of ansible
Learn Ansible on Udemy with Offers
Learn how to use Ansible to automate local and cloud configuration management tasks on Udemy with Min 50% offer.
Ansible installation is very easy and configured easily.
Writing a script in the YAML file is very easy and powerful.
Executing the commands remotely makes the accessibility of the target system easy.
Ansible commands are executed in sequential order so that understanding of the script execution is easy.
Ansible can be executed N number of target servers as per the inventory file.
Shares facts between multiple servers, so they can query each other.
Agent-less deployment makes faster connections compared to an agent-based model.
Compared to the connection protocols of other tools, SSH and winRM connections are secured as compared to other models.
SSH communications are slow which may cause more downtime.
Compared to other tools limited features like monitoring, API availability.
The syntax for The Playbooks and Templates is different which may be a little difficult for beginners.
The Chef is the client-server architecture model configuration management tool. The scripting of this tool is written in Ruby DSL using imperative programming paradigm. The Chef is using the pull-based approach to send Configuration information to the target nodes. Chef uses the agent-based system where target servers are installed with an agent called chef-client which will poll the instruction from the master server that responds with SSH connection. Let us see the basic architecture of the chef.
There are three important components are present in the chef architecture. Client Nodes are the nodes which need to be configured by installing agent application called chef-client. Chef Workstation is the authors working machine where the author writes the Ruby DSL called cookbook and test with the testing tool called Test Kitchen and communicate with the chef server using the command line or knife tools. Chef Server is a common server between workstation and chef-client. This server will keep the cookbook, policies, and metadata of the nodes or chef clients. Chef client will pull the recipes and templates and it will install in the node.
Learn Chef on Udemy with Offers
Learn Configuration Management with Chef to automate local and cloud tasks on Udemy with Min 50% offer.
Completely programmable, so that scope of handling and customization is very high
The chef is also executing commands in sequential order which is very easy to understand the flow.
Chef’s Community is very active and it has Strong documentation and support.
One of the most flexible solutions for OS and middleware management.
The chef is well matured and stable for large-scale deployment.
SaaS version of Chef is available which is very useful for analytics and reporting.
Beginners required huge learning and it is very difficult for them.
Configuring the chef and initial setups are complex.
The pull-based configuration will wait for the next scheduled polling to get the configuration from the server.
Puppet
Puppet is another opensource configuration management tool and vastly used by many teams. It is also using ruby declarative language (Ruby DSL) to configure the files. Puppet can either configured with a client-server (Agent-master) architecture model or stand-alone architecture model.
Agent/master architecture: Puppet-master will keep the configuration and controls it, Puppet agent nodes will request or pull the configuration information and configure the same on the node. A report will be sent to the puppet master once after the configuration is updated. Communication between master and agent will happen via an HTTPS connection.
Stand-alone architecture: Every node will be installed with the puppet application. Each node will be carrying its own configuration information. By running Puppet apply command, the nodes will be configured according to the configuration information. Usually, this will happen in a scheduled job or with a Cron job.
Learn Puppet on Udemy with Offers
Learn Fundamentals of Puppet to automate local and cloud configuration management tasks on Udemy with Min 50% offer.
Initial setup and configuration is very easy
Web UI console will help us to take care of many configurations, reporting, and real-time node management tasks easily.
Puppet is very Robust and has native capability to work with shell-level constructs.
Very stable and matured system for the DevOps guys to manage large scale infrastructure
Puppets’ Community is also very active and it has Strong documentation and support.
Some times it is difficult for beginners to learn Puppet DSL or Ruby,
We need CLI for doing advanced tasks.
The Ruby DSL code can go big when we scale higher and it will become complicated.
As always, the pull-based system follows a scheduled job for tasks which will make us wait for configuration.
Puppet DSL is a little different than Ruby so that pure Ruby won’t work some times.
Selection of the right configuration management tool is relative to the situation and system. Comparing the pros and cons of each tool and understanding the architectural design will help us select the right tool for configuring our infrastructure.
Get more knowledge on DevOps from this
Conclusion
In this article, we have discussed the pros and cons of Ansible vs Chef vs Puppet. Also, take a look at our discussion on Ansible Playbook and Ansible Inventory. We will discuss more these configuration tools in our future discussions and article. Stay tuned and subscribe DigitalVarys for more articles and study materials on DevOps, Agile, DevSecOps, and App Development.
Experienced DevSecOps Practitioner, Tech Blogger, Expertise in Designing Solutions in Public and Private Cloud. Opensource Community Contributor.
Chef and puppet
Chef and puppet
Chef and puppet Breaking news today Chef and puppet
Chef and puppet
This article covers the complete comparison of Ansible vs Puppet vs Chef with detailed explaination and pros - cons of every tool.
Chef and puppet
Chef and puppet Chef and puppet Chef and puppet
SOURCE: Chef and puppet Chef and puppet Chef and puppet
#tags# -,-Chef and puppet] Chef and puppet#tags#
Kabrinskiy Eduard
online news |
Эдуард Кабринский - Azure devops automation - Рдуард Кабринский
Azure devops automation
Azure devops automation National news Azure devops automation
DevOps and Automation: The Azure License Tool
There's a new tool on the block that wants to help you manage your multiple Azure licenses.
Join the DZone community and get the full member experience.
This new tool wants to help you manage your Azure licenses
Background
Managing an Azure DevOps license with a global enterprise organization could be a real challenge.
Usually, the global organization is operating in many cities and different countries with hundreds of projects and maybe hundreds of thousands of engineers who keep joining new projects or rolling-off from many others every day.
So, you may end up with hundreds or thousands of Azure DevOps licenses that are not being used anymore, and maintaining them, downgrading them, or freeing them up became a real challenge.
Therefore, I developed a new tool which published on Azure DevOps Marketplace that will solve all these problems and automate that process.
The following video explains in detail what is the challenge, how to install the prerequisites and how to use the tool.
The Challenge of Managing Azure DevOps for a Global Enterprise
As I explained before managing an Azure DevOps license with global enterprise organization is a real challenge due the natural sprawl of the global organization.
The Challenge of Managing Azure DevOps for a Global Enterprise
Intro to the Azure DevOps Recycling License Tool
Here are some of the features that the tool has:
Free up unused license based on a configurable duration
Downgrade Basic and Basic + Test Plan to Stakeholder based on a configurable duration
Several switches to enable and disable all options
Dry run to validate and verify the actual action before it takes place
Well descriptive logging into the screen as well as a file system.
Integrating Recycling License Tool With Azure Pipeline for a Full Automation Process
We can integrate the Recycling License tool with Azure Pipeline using a schedule trigger to have a full automation process for freeing up, downgrading or managing Azure DevOps license.
Installing the Prerequisites
Explaining the Configuration File of The Tool
add key=”dryRun” value=”true” />
(dryRun) option, possible values
This option is to validate all the process before running the actual actions, and is the main switch to run the tool or just validate all actions. It’s advisable to run at least a one-time dry run and verify the result if it’s as expected or not before running the actual run.
add key=”orgName” value=”your org name” />
(orgName) option, possible values text with org name only
This option is the name of the Azure DevOps organization.
add key=”orgUrl” value=”https://dev.azure.com/your org name” />
(orgUrl) option, possible values text as URL
This option is the URL of the Azure DevOps organization.
add key=”personalaccesstoken” value=”mo6rjfzh6g77gn6xu” />
(personalaccesstoken) option, possible values PAT value
This option is the access token will be used to get the list of users with their information, and it’s advisable to use a token with minimum permissions like read without edit but on the organization level. The actual action, like removing or downgrading license, will require you to login with a proper account which has high permissions to change the license or remove users from the organization.
(enableDowngradeUserLicense) options, possible values
This option will enable or disable downgrade license from Basic and Basic +Test Plans to Stakeholder. So, by disabling this with a false value, there is no action will be taken. Remember if you enable this option by setting it to true with the dry run option set to true, this will show you how many users will be downgraded without really downgrade them.
(durationToDowngrade) option, possible values integer number
This option is the duration in days required to downgrade a license from Basic and Basic +Test Plans to stakeholder if they are not active for that duration.
(enableRemoveUserFromOrganization) option, possible values
This option will enable or disable remove users from Azure DevOps organization. So, by disabling this option with a false value, there is no action will be taken, remember if you enable this option by setting it to true with the dry run option setting to true, this will show you how many users will be removed without a real remove them from the organization.
(durationToRemoveUserFromOrganization) option, possible values integer number
This option is the duration in days required to remove a user from Azure DevOps organization if they are not active for that duration.
Explaining The Configuration File of Recycling License for Azure DevOps
Run the Tool in A Dry-Run Mode for Validation
It’s very important to run the tool in dry run mode for the first time then review and verify if the result and the logged information is the expected results before running the actual mode.
pid="178">
Run The Tool in a Dry Run Mode For ValidationRecycling License
Review the Log File
You can review the log file for any dry run or actual run.
Review the log file of Recycling License for Azure DevOps
Login to Azure DevOps
Before you run the actual mode, you need to login to Azure DevOps with an account that has privileges to downgrade license or remove users.
You will login using Azure CLI login command (AZ login).
Login to Azure DevOps organization
Run the Tool in An Actual Mode to Real Execute the Actions
Once you are logged in and have verified the result before in a dry run, you're ready to run the actual mode to make the tool takes real actions.
Run The Tool in an Actual Mode To Real Execute The Actions for Azure DevOps Recycling License Tool
Further Reading
Azure DevOps Build Pipeline for Jekyll
Build and Deploy an ASP.NET App With Azure DevOps
Published at DZone with permission of Mohamed Radwan , DZone MVB . See the original article here.
Opinions expressed by DZone contributors are their own.
Azure devops automation
Azure devops automation
Azure devops automation Today news live Azure devops automation
Azure devops automation
With global organizations that have potentially thousands of developers, this tool can help keep manage the multiple Microsoft Azure licenses.
Azure devops automation
Azure devops automation Azure devops automation Azure devops automation
SOURCE: Azure devops automation Azure devops automation Azure devops automation
#tags# -,-Azure devops automation] Azure devops automation#tags#
Kabrinskiy Eduard
daily news |
DennisBup
MichaelRor
Gandistrugh
charityew11