Skip to main content

Windows Live - Introducere

Windows LIVE series:
Acesta este primul post dintr-o serie de posturi in care osa discutam despre Microsoft Live ID. O sa discutam mai ales din perspectivaunui dezvoltator. Inainte sa incepem sa vorbim despre Live ID, cred ca estenecesar sa vedem ce inseamna OpenID.
OpenID is an open standard that describes how users can be authenticated in a decentralized manner, eliminating the need for services to provide their own ad hoc systems and allowing users to consolidate their digital identities.
Sursa: Wikipedia
Pentru noi, ca si dezvoltatori de aplicatii web, mobile saudesktop acest lucru inseamna ca putem sadezvoltam aplicatii care permit utilizatoriilor sa se autentifice cu un user deLive Id, Facebook, Yahoo, Google. Open ID ne ofera mecanismul prin care putemsa verificam identitatea unui user, userul X este perosana care predinte caeste defapt.
Din cei trei de AAA(Authentification, Autorization, Accounting), OpenID ne ajuta sa rezolvam primulA – Authentification. In general, partea de autorizare si de tracking trebuiesa o facem in interiorul aplicatiei noastre. Uneori exista mai multe sistemecare sunt integrate intre ele, a.i. partea de autorizare se face intr-un singurloc, dar acesta este un caz particular.
Exista mai multe moduri prin care un user se poateautententifica in system folosind OpenId( url, token, password, smart cards,amprenta etc). OpenID fiind un standard nu impune modul prin care un usertrebuie sa se autentifice.
In procesul de autentificare folosind OpenID sunt implicate 3sisteme care comunica intre ele:
  • User device – deviceul de pe care userul vrea sa accesezeaplicatia noastra
  • Identify Provider (OpenID provider) - sistemul pe care il folosim pentruautentificare
  • Relying Party – aplicatia noastra
Scenariul este urmatorul:
Un user doreste sa se autentifice in aplicatia noastra. In locsa introduca user si parola, acesta o sa selecteze Identify Provider-ul pe careil foloseste. Identify Provider nu trebuie sa fie neaparat unul cunoscut.Userul poate sa introduca doar un URL si sa predinta ca URL-ul respective estea lui. Relying party trebuie sa contacteze identify provider si sa asociezerequestul facut de user (in general intre indentity provider si relying partyse face un schimb de token-uri). Dupa acest pas relying party o sa faca unrequest de autentificare la idenfity provider, care o sa deschida o fereastrade log-in la end-user. Userul isi va introduce credentialele lui, care urmeazasa fie verificate de catre identify provider. Dupa acest pas identify providero sa raspunda la relying party daca autentificarea a avut loc cu success. Pebaza acestui raspuns userul se va autentifica in sistemul nostru.
Raspunsul care vine de la identify provider nu o sa vina asaimediat. In functie de cat de repede introduce userul credentialele, raspunsulpoate sa vina in 10 secunde sau in 2 minute. Exista diferite implentari pentrumecanismul prin careidentify provider notifica relying party daca autentificareaa avut loc cu success. In implementarea standard, identify provider apeleazarelying party (se face un submit la o anumita adresa) si ii trasmite dacaautentificarea a avut loc cu success.
Mai jos puteti sa gasiti modul in care se schimba informatia in momentul in care se foloseste OpenID.
1. Send user’s URL
2. Redirect user to get token from OP
3. Get token from OP
4. User post credentials to OP
5. Redirect token is send back to the relying partyusing user device
6. Redirect token is send back to the relying partyusing user device

Dupa cum ati putut observa in schema de mai sus, inate saputem folostii un provider de Open ID este necesar sa ne inregistram la acesta.
In general fiecare identify provider ofera diferitefunctionalitati pe langa cele de baza( informatii suplimentare despre user:nume, sex, varsta, language, etc).
Microsoft Live Id-ul este mecanismul de identify provider pecare il foloseste Microsoft. Acesta nu trebuie folosit doar de catreaplicatiile Microsoft, poate sa fie folosit in orice fel de aplicatie. Existamai multe modalitati prin care ne putem creea un count de Live Id, uneori necream unul fara sa ne dam seama. Daca avem un cont de Hotmail, WindowsMessenger sau .NET Passport atunci deja avem si un cont de LiveId.
Din punct de vedere istoric, prima data a aparut Hotmail,urmat de .NET Passport, iar apoi Windows Live ID. Din 2007 Microsoft a lansatSDK-ul de Live ID prin intermediul caruia orice dezvoltator, putea sa integrezeLive ID in aplicatia lui, indiferent de limbajul si/sau platforma. Din 2008, Microsofta anuntat ca suporta standardul OpenID in totalitate.

Comments

Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…