Top Contributors Awards!! System Center, Active Directory, T-SQL, C#, Gurus and Greatness!!

Comments

Post a Comment

Popular posts from this blog

Run Android emulator and Android Studio on Azure VM using Hyper V

Image
14 min to read. Abs07act Due to Corona outbreak, times are hard! Please take care everyone! I wish good health for all! Stay safe! There is another outbreak I am seeing – Making Development environment available on Azure to enable Work from home. Almost in every customer call I hear about requirement to enable Development Environment on Azure and accessing it from Home laptop/ PC and continue the business. In the era of “Mobile first” almost every big enterprise, every Small and Medium Business (SMB), every Start up company have mobile development teams. They use variety of tools and one of the important IDE used for Mobile development is “Android Studio”. Installing and running Android studio is smooth; however Android emulator installation fails on Azure VM. It is not s07aight forward. In this blog we will see “how to enable Android emulator with Android Studio on Azure VM”. Let’s go! Concept - Android Emulator and VM Acceleration Without a virtualiza...
Read more

The request has both SAS authentication scheme and 'Bearer' authorization scheme. Only one scheme should be used

Image
While doing testing after doing a POC on Securing Logic App with Azure Active Directory authentication , where I have put logic app behind APIM and before passing the request to logic app, apim does validation of the token.  I was encountered with an error "The request has both SAS authentication scheme and 'Bearer' authorization  scheme.  Only one scheme should be used." Why it happened After validating the token which is part of the header i.e. Authorization, APIM forwards the request as it is to backend. As  Logic app is configured as  back end , it's url already consist of SAS signature plus the request also has Authorization section and this is the problem. By default every request endpoint on a logic app has a Shared Access Signature (SAS) in the endpoint's URL, which follows this format: https://<request-endpoint-URI>sp=<permissions>sv...
Read more

Azure AD Token Generator using .NET Core

Image
10 min to read. Abs07act Change is inevitable. With .NET Framework becoming legacy and .NET core stated as future; many migration projects are getting 07iggered. Also for new projects, development choice is .NET core by default. Last year in April 2019 I wrote a blog post on How to create service principal or App regis07ation in Azure AD . This is one of the most visited blog post. Reason is simple. Any functionality having requirement of invoking Azure REST API requires Azure AD token generation. This helps in performing management tasks against Azure environment; and hence it is crucial. The last year blog is based on .NET framework. With .NET core becoming more and more obvious choice, I thought it is time to have new blog post and new code base for “.NET core based Azure AD Token generator using Service principal.” Let’s go! Why I need to generate the Azure AD Token? This is common question I get. What are the scenarios where I need to generate Azur...
Read more