Skip to main content

Windows Live - Web Authentication

By
Windows LIVE series:
Live ID se poate folosii pentru doua lucruri:
  • autentificarea userilor in aplicatia noastra folosind contul de Live ID
  • accesul aplicatiei noastre la servicii pe care un user de LIVE ID are access( photo sharing, agenda, calendar, etc)
Astazi o sa discutam despre cum poate un utilizator sa se autentifice in aplicatia noastra folosind contul de de Live ID.
Mai jos o sa prezint vechiul mod de autentificare, care a devenit absolute, odata cu lansarea "Live Connect", despre care o sa povestim cat de curand. Prefer sa prezint si acest mecanism in cazul in care lucrati cu aplicatii deja facute care folosesc vechiul mecanism de autentificare.
Acest mecanism de autentificare a fost denumit de cei de la Microsoft "Windows Live ID Web Authetification", dar nu are nimic mai special. In momentul in care userul doreste sa se autentifice, acesta este redirectat spre pagina Windows Live ID, unde isi va introduce datele. Dupa acest pas, userul este redirectat inapoi spre aplicatia noastra cu o cheie unica( token) - denumita Cliend ID, pe baza careia putem sa identificam userul. Pe langa aceste informatii, avem access la cateva date de baza a userului precum nume, tara, etc.
Cliend ID este o cheie unica formata din 16 caractere, pe care o sa trasmiteti la servere Windows Live de fiecare data cand un user se autentifica. Toate datele care se trasmit o sa fie encriptate si semntate pe baza unuei chei secrete pe care o primiti in momentul in care va inregistrati aplicatia.
Primul pas pe care trebuie sa il facem este sa ne inregistram aplicatia. Fiecare aplicatie se identifica unic pe baza unei chei. Acest lucru se poate face la urmatorul link: http://go.microsoft.com/fwlink/?LinkID=144070
Odata ce avem aplicatia inregistrata, trebuie sa adaugam in aplicatia noastra un link de autentificare prin Live ID. Acest link o sa contina ca si parametrii:
  • appid - cliend ID( cheia unica a aplicatiei noastre)
  • context -( optional) pagina spre care userul sa fie redirectionat dupa ce autentificarea se finalizeaza( ex. welcome.html)
  • style -( optional) o colectie de atribute folosite prin care se poate personaliza bunoul de sign in
Dupa ce userul isi introduce credentiale o sa fie redirectionat spre pagina noastra. Pe flowul normal, in cookies o sa gasim un token encriptat cu cheia "webauthtoken". Acesta o sa contina urmatoarele date despre user:
  • User.Id – id-ul unic a fiecarui user
  • User.Timestamp – data ultimei autentificari
  • User.Context – contextul care a fost specificat in momentul autentificarii
  • User.Token – token-ul unic a userului curent( dupa o anumita perioada de timp acesta o sa expire)
Trebuie precizat ca datele sunt encriptate este AES128, iar cel de semnare este HMAC-SHA256. Mai jos gasiti un exemplu de cum trebuie facuta decriptatea si extragerea datelor.
public string DecryptResponse(){     const int ivLength = 16;     token = HttpUtility.UrlDecode(token);     byte[] ivAndEncryptedValue = Convert.FromBase64String(token);     var decryptAlg = new RijndaelManaged();     decryptAlg.KeySize = 128;     decryptAlg.Key = cryptKey;     decryptAlg.Padding = PaddingMode.PKCS7;     var memStream = new MemoryStream(ivAndEncryptedValue);     byte[] iv = new byte[ivLength];     memStream.Read(iv, 0, ivLength);     decryptAlg.IV = iv;     cStream = new CryptoStream(memStream, decryptAlg.CreateDecryptor(),                          CryptoStreamMode.Read);     sReader = new StreamReader(cStream, Encoding.ASCII);     return sReader.ReadToEnd();}

In urmatorul post o sa discutam despre Live Connect.
Labels:

Comments

Post a Comment

Popular posts from this blog

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

By
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(
Post a Comment
Read more

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

By
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.51 EF 6.0.2 VS2013 It see
8 comments
Read more

Navigating Cloud Strategy after Azure Central US Region Outage

By
 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too
Post a Comment
Read more