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

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP