(requires PAT which can be created using these directions ) DevOps PHP Sample for Cory Fowler and his PHPWorld Presentation - Ozzie Rules Blogging - Site Home - MSDN Blogs.also use the newly introduced personal access tokens (you can read more about that in this post of Rene van Using JSON via REST to create build definitions in VSO | ALM by Erick Segaar.Personal Access Tokens are a more secure way of a Personal Access Token (PAT) to access Visual Studio Online through the app. Quick start on making an Apache Cordova app to connect to Visual Studio Online | Code Smells.The great thing is that you can revoke rights or the token afterwards and make sure that people cannot access stuff anymore. So when you now clone a Git repository you only have to fill in this token in the password box. This token alone is sufficient to authenticate against VSO. When you create the token, you see a token (only visible after creation !) that you should copy and keep safe. For example a token to access Code Features. On the page you can configure one or more Personal Access Tokens. Instead of sending our username and password over the wire we an now use a secure token that we can scope to a timeframe and to functionality within VSO.
In the update of July 7th, we now have the ability to use Personal Access Tokens as an alternative to the Alternate Credentials. This is great but not the most secure way of doing things. Once you enable your credentials, you can use these credentials when doing a REST call or (easier to test) clone a Git repository You configure your alternate credentials on your page and fill a username and password of your choice. These are used when accessing the REST API or when using an external client for accessing your Git repositories. People who use Visual Studio Online for a while are probably familiar with the alternate credentials.
0 kommentar(er)
